Managing Off-Cycle Payments

This chapter provides an overview of off-cycle processing and discusses how to:

Note. Please refer to PeopleSoft Enterprise Global Payroll 9.0 PeopleBook for information on off-cycle setup and processing.

See Also

Configuring Off Cycle Transactions

Managing Off Cycle Processing

Click to jump to parent topicUnderstanding Off-Cycle Processing

This section discusses:

Click to jump to top of pageClick to jump to parent topicThe Off-Cycle Process

Off-cycle payroll processing refers to processing payments and making corrections to finalized results outside of the normal payroll schedule. Off cycle transactions are typically made to correct prior payments or to make early termination payments that can't wait until the next scheduled on cycle payroll.

Click to jump to top of pageClick to jump to parent topicTypes of Off-Cycle Transactions

The four types of off-cycle transactions are:

  1. Manual payments

    Manual payments enable you to enter payments that you have calculated and paid outside of the payroll system. Examples include paying a new hire with a manual check, because their pay details were not entered in time for the normal pay run.

  2. Corrections

    Corrections enable you to correct results of any finalized payroll. Examples include recalculation due a sickness not entered in the system on time or unpaid overtime.

  3. Additional payments

    Additional payments enable you to enter one-time payments that fall outside the normal payroll process. Examples include one time bonuses or expense reimbursement.

  4. Advances

    Advances enable you to pay payees before their normally scheduled pay run. Examples include salary due on termination.

Click to jump to parent topicRecording Manual Payments

Manual Payments are payments that you record for items that you calculate and pay outside of the system, such cash or check payments. In Spain manual payments might correspond to advances, expenses, or special payments such a bonus or a commission paid out the regular cycle.

When entering manual payments for Spanish payees, it is recommended that all calculations be manually calculated outside the system and then entered. The following areas need to be considered carefully when entering manual payments:

Note. Manual payments are used to record monetary values only, absence accumulators will not be updated using this method.

Click to jump to parent topicProcessing Payroll Corrections

The payroll corrections functionality of off-cycle payroll processing enables you to change finalized results for specific employee and calendar combinations due to such things as user error or missing information.

A common cause of missing information is that your company might run payroll before the end of the month to ensure that employees receive their money by the last day of the month. Because of the early payroll run there might be missing information from the remaining days of the month that you need to report to Social Security, such as terminations, hires, sicknesses, and overtime.

Global Payroll for Spain provides two options for reporting the missing information to Social Security in a FAN file.

One option for reporting the missing information to Social Security in a FAN file is to wait until the next payroll and run retroactive processing of payroll as part of the payroll calculation for the subsequent month to correct the payroll and pay for differences. You must report this retroactive processing information in a complementary FAN file when generating the FAN file for the subsequent month. Due to reporting the information late, Social Security charges a surcharge. Global Payroll for Spain calls this running a pure retroactivity.

To avoid paying the accompanying surcharge for the complimentary FAN file report, you can use off-cycle processing to make payroll corrections for the affected payroll. You can run a correction in two different ways:

Note. Technically, a payroll correction is a retro calculation where the system behavior is changed to deliver Social Security and tax data in a different way using Global Payroll for Spain elements.

There are two ways to run a payroll correction of a finalized payroll:

There are two ways to run a payroll correction of a finalized payroll:

Running Corrections Using a Specific Run Type

To run a payroll correction using a special calendar with a specific run type of CORRECCION:

  1. Run the regular payroll for the month, finalize it, and pay it.

  2. Enter new data that impacts that payroll run.

  3. Create a correction calendar using the Calendars component or the Calendars - Automated Creation component.

    System will automatically run a correction for all the employees affected by pending changes, provided that the calendar and calendar group meet the following criteria:

  4. Run the payroll for the correction calendar to perform the correction calculation.

  5. Run the banking process for the off-cycle calendar group to pay employees the difference between the regular payroll calculation and the correction payroll calculation.

  6. Generate monthly legal reports.

  7. Generate payslips:

The following example illustrates how to process a payroll correction for Global Payroll for Spain. Let's say that you run the regular payroll for January on January 25. To do so, create the corresponding calendar and calendar group called ENE PAYROLL. On January 30th finalize the January payroll and run the banking process for the calendar group ENE PAYROLL.

On February 2 the payroll administrator receives positive input about overtime for EMP1 that corresponds to the January payroll calendar. (Note that in this example we assume there is a retro trigger defined for GP_PI_MNL_DATA.) On February 5 the payroll administrator realizes that there was no reduction entered for employee EMPL2 and enters the reduction at the contract data level. (Note that in this example we assume that there is a retro trigger defined for CNTRCT_DATA_ESP. IN both of these cases the system generates a retro trigger for each of these employees that will cause retroactive processing for January the next time that you run the payroll process. You can check which employees are impacted by retro calculations on the Review Triggers page by navigating to Global Payroll & Absence Mgmt, Absence and Payroll Processing, Prepare Payroll, Review Triggers.

On February 15 the payroll administrator wants to run a correction of January payroll to consider all the changes that happened after it was run. He doesn’t want that this correction will cause Social Security complementary reporting due the fact he is still Note that because the payroll administrator is still on time to generate the FAN file for January the company does not have to submit a complementary FAN file to Social Security and does not incur the corresponding surcharge. The payroll administrator creates a calendar group containing just one calendar with the necessary conditions for running a payroll correction.

The payroll administrator runs the new calendar group and, after checking results, finalizes the payroll run. To pay differences, the payroll administrator runs the banking process for the calendar group ENE CORRECCION. The process generates a banking file that contains just the delta between the first payroll run ad the correction calculation.

When the payroll administrator or another user runs tax or Social Security reports, the system uses the recalculated values. For the FAN file, the report includes modifications that were made in February affecting January in the regular report, not a complementary report.

The payroll administrator can generate payslips for January, printing one payslip for the ENE PAYROLL calendar group that corresponds to the first payroll calculation for January and another payslip for the ENE CORRECCION calendar group that corresponds to the delta calculation between the first calculation and the correction calculation.

Running Corrections Using Off-Cycle Functionality

Global Payroll for Spain delivers off-cycle configurations for corrections off-cycle requests that are related to the following reasons: new hires, new terminations (for terminations after the first payroll run), and payroll correction. Define configurations for off-cycle requests on the Off-Cycle Configuration page.

To run corrections using core Global Payroll off-cycle functionality:

  1. Run the regular payroll for the month, finalize it, and pay it.

  2. Enter new data that impacts that payroll run.

  3. Create an off-cycle request.

    Navigate to Global Payroll & Absence Mgmt, Absence and Payroll Processing, Off Cycle, Off Cycle on Demand and perform the following steps:

    1. Select as Target Period ID the period that you want to correct.

    2. Create a request by providing the information about the off cycle processing that you want to run.

    3. List the employees for which you need to enter data to correct the finalized payroll in the Corrections - List Payees and Calendars grid.

    4. Access the Correction Request Details page to enter the calendar to correct.

    5. Click the PI Calendar to Correct link to enter the positive input into the finalized payroll that you want to correct.

    6. Click the Absence Event Entry link to enter absences affecting the finalized payroll that you want to correct.

    7. Provide a supporting element override in the target calendar by accessing the supporting element overrides, clicking the Target Calendar link, and entering a value 1 for the variable CLI VR CORRECCION.

  4. Create a calendar group on Off Cycle On Demand page.

  5. Click the Calculate button on the Off Cycle On Demand page to run the off-cycle processing and perform the off-cycle calculations.

  6. Click the View Status and Results link to check processing results.

  7. Finalize the off-cycle processing so that you can pay the delta.

Click to jump to parent topicMaking Additional Payments

Use the additional payments functionality that is part of off-cycle processing to make one-time unscheduled payments that are processed outside of the normal on-cycle payroll. Examples include one-time bonuses, awards, and expense reimbursements. These transactions are similar to manual payments in many respects; however, the system calculates the amount for additional payments.

The following areas need to be considered when entering additional payments:

Click to jump to parent topicIssuing Advance Payments

Advance processing is the processing of on-cycle calendars ahead of their regular schedule. Use the advances functionality of off-cycle processing when you would like to pay an employee before their normal on-cycle pay run. Examples include payments for early terminations (where the termination payment needs to be paid immediately and not in the next on-cycle pay run), full periods advances, and partial period advances.

The following is recommended when making advance payments:

Global Payroll for Spain delivers an off-cycle configuration for advance payments off-cycle requests that you can use for advance terminations. Define configurations for off-cycle requests on the Off-Cycle Configuration page.

See Also

Configuring Off Cycle Transactions