Understanding Year-End Rollovers

You use rollover programs to carry forward balances for pay types, deductions, benefits, and accruals (PDBAs) at the end of the year and to create the beginning balances for the next year. You need to carry forward these balances to correctly process payroll cycles in the new year. You should process year-end rollovers after you process the last payroll cycles of the year. The rollover program uses the previous year's deductions, benefits, nad accruals (DBA) balances to create beginning balances for the new year.

For PDBAs with ending balances that you do not need to calculate, the system rolls over the accumulated total to the new year. No special PDBA setup is necessary. For benefits and accruals with balances that you need to calculate first, you must set up rollover information for the DBA. (For example, before the balance is rolled over, you might need to subtract vacation that the employee took from the available vacation.)

You can process year-end rollovers in proof or update mode. Processing rollovers in proof mode enables you to review information and make necessary corrections before updating history tables. Processing rollovers in update mode enables you to update history tables with beginning rollover balances.

The Payroll system provides two types of rollover programs for year-end processing:

Rollover Program

Description

Calendar month rollover

Use the Calendar Month version of the Year-End Rollover program (P07390) to process DBAs that roll over balances at the end of the standard year, according to work dates. This program uses the previous year's deduction, benefit, and accrual balances to create beginning balances for the new year. Run this program after you process the last payroll with work dates in the current year.

The system maintains historical balances for the calendar month year in the Calendar Month DBA Summary History table (F06145).

Payroll month rollover

Use the Payroll Month Version of the Year-End Rollover program to process DBAs that roll over balances at the end of the standard year, based on payment dates. This program uses the previous year's DBA balances to create beginning balances for the new year. You should run this program after you process the last payroll with a payment date in the current year.

The system maintains historical balances for the standard year in the Employee Transaction History Summary table (F06146).

The system maintains balances in different tables because of the differences between calendar months and payroll months. For example, when a pay cycle crosses calendar months, monthly DBA totals are different for the payroll month and calendar month, but year-to-date (YTD) totals remain the same (unless the cycle also crosses calendar years).

The system rolls over DBAs that have any of these situations:

  • Remaining balances

  • Remaining periods

  • An inception-to-date limit

  • An annual carryover limit

  • Deduction amounts due

  • Arrearages

    Note: Rolling over wage attachment DBAs that are administered using the Wage Attachment module is not necessary. The system automatically continues to calculate wage attachments for the new year without calculating rollover balances.

You must run the Year-End Rollover program using these processing modes before you run the first payrolls of the new year:

  • Payroll Month Rollover

  • Calendar Month Rollover

You use the Payroll Month Rollover mode to process payroll-month rollovers after the last payment date of the current year and before the first payment date of the new year. You do not need to consider work dates within a payroll cycle when deciding when to run the Year-End Rollover program using this processing mode, because it is based solely on payment date.

You use the Calendar Month Rollover mode to process calendar-month rollovers after the last payroll with work dates in the current year. You do not need to consider payment dates of a payroll cycle when deciding when to run the Year-End Rollover program using this processing mode, because it is based solely on work dates.

This table lists examples illustrating when you should run the rollover programs:

Pay Period Ending Date

Payment Date

Run Calendar Month Rollover

Run Payroll Month Rollover

December 31, 2023

December 31, 2023

After this payroll

After this payroll

December 31, 2023

January 04, 2024

After this payroll

Before this payroll

January 04, 2023 with work dates in 2023 and 2024

January 04, 2023

After this payroll

Before this payroll

January 11, 2024 with no work dates in 2024

January 11, 2024

Before this payroll

Before this payroll

This table illustrates how the JD Edwards Payroll system maintains balances for the standard year for all PDBAs:

Version

Table

Based on

Calendar Month Rollover

Calendar Month DBA Summary History table (F06145)

Work dates

Payroll Month Rollover

Employee Transaction History Summary (F06146)

Payment dates

The system updates the Calendar Month DBA Summary History table by work date and the Employee Transaction History Summary table by payment date. You use the same program to process both types of rollovers.

First, run the rollover program without updating the history tables. The system identifies possible errors without changing any information in the history tables. To locate any errors, review the reports that are generated by the rollover programs. After you correct any errors, rerun the rollover programs in update mode.

If an employee has sick or vacation pay history in multiple companies, the system combines all hours for each pay type before subtracting the total hours from the combined history for the related accrual.