Your organization might have multiple pay groups in a pay run. Dayforce can accommodate situations like this by sequentially validating and committing the pay groups in the pay run by configuring concurrent commit controls functionality in Dayforce.
Before You Begin: This topic describes the concepts you should understand before configuring concurrent commit controls for payroll. If you are already familiar with this content and only need configuration instructions, see Configure Concurrent Commit Controls.
In some cases, you might have some employees in more than one pay group, and some pay groups might fall in the same pay run. When this happens, these crossover employees can cause an employees crossing pay groups condition. Having crossover employees can result in validation and calculation errors that can prevent the sequential validation and committing of pay groups in the pay run.
Configuring Dayforce to use concurrent commit controls functionality makes it possible for employees to be in multiple pay groups in the same pay run and still allow pay run validation and calculation to succeed. Using this functionality, the application automatically recalculates the crossover employees in the subsequent individual pay groups that are in the sequence of pay runs being committed.
Concurrent commit controls are important for protecting the integrity of year-to-date and limit calculations for an employee with calculations in more than one pay group that are part of the same pay run.
You can review the impacted employees again before revalidating and committing pay runs, or you can configure the application to make recalculation an automatic step of the commit process without manual intervention. When you select the Enable multi-pay run commit of pay runs with mutual employees checkbox, you configure the application to allow seamless committing of sequential pay runs in Payroll > Overview, which can improve efficiency of simultaneous sequential commits.
When you select the automated option, be aware that the impacted employees will be recalculated subsequent to the locked preview. You cannot preview the results again before continuing the commit process.
Important: When Dayforce calculates data in a pay run, year-to-date and limit tracking are based on the <latest committed data> plus the <current calculated amount>. Recalculation does not include uncommitted data. If pay dates are committed out of sequence, year-to-date amounts will reflect only what is committed until a subsequently dated pay run is committed.
You can perform more than one preview calculation on a single employee, but the application does not include calculations from one currently-running preview in another currently-running preview.
Both previews are locked for calculation and submitted for sequential commit. This ensures that the results of the first commit are used in the recalculation of the year-to-date and limits amounts of the second commit. Pay runs being committed sequentially must be automatically validated and recalculated as part of the sequential commit process. Pay runs cannot be committed until automatic recalculation has completed.
Configuring concurrent commit controls involves the following client properties in the Payroll section of the Properties tab in System Admin > Client Properties:
- Enable Concurrent Calculate: Select to allow one pay run to load while Dayforce is calculating another pay run.
- Require recalculation after committing pay runs with mutual employees: Select to set concurrent commit controls to force the recalculation of crossover employees between commits. This checkbox is selected by default.
- Enable multi-pay run commit of pay runs with mutual employees: Loads when you select the Require recalculation after committing pay runs with multiple employees checkbox. Select this checkbox to configure automatic recalculation after the lock without the need to review before committing. This allows sequential pay runs to be committed seamlessly.