Plan Year Dates for Ongoing Exports

Dayforce Implementation Guide

Version
R2025.1.1
Plan Year Dates for Ongoing Exports

Before You Begin: It’s assumed that all of the plans associated with the carrier have the same plan year start and end dates. In turn, you must set up your export configuration to use the same Plan Year Start Date and Plan Year End Date values that you’ve defined for the plans associated with that carrier in Benefits Setup > Plans and Options.

Dayforce uses the Plan Year Start Date and Plan Year End Date values of the export configuration to control the look-back and look-forward period of the background job. This ensures that the benefits data in the export file doesn't cross plan years. For example, you select a relative date type and enter date values of January 1 and December 31.

If you run the export job on December 30, with a look-forward period of 100 days, the job only looks forward to December 31 because it won't cross the plan year.

In addition, end date values for the election and coverage aren't included in the export file if those values are greater than the look-forward period that was selected when the job was run (or the plan year end, if that comes first). This reduces the risk of a carrier improperly ending an employee's election before receiving the employee's new election for the upcoming plan year.

For example, an organization's Open Enrollment takes place between October 1 and 15. Several employee elections will be ended on December 31, the day before the new plan year elections begins. If the ongoing file is sent on November 1 with a look-forward period of 30 days, the end date value isn’t included in the file for those elections ending on December 31. The field is left blank, and the value isn’t included in the file until December 1, when it falls within the 30-day look-forward period.

Because the background job runs based on the current date (that is, the date that you run it), if you use the fixed plan year date type in your export configuration, those dates must be for the current plan year to ensure that the background job runs properly. In other words, the date on which you run the background job must fall on or between the Plan Year Start Date and Plan Year End Date values.