3788358 - Incorrect Start Date for Recurring Deduction and Recurring Information for Benefit Integration records - 1H 2026

An issue was identified in benefit enrollments processed through Benefits Exception.

Benefits Exceptions are commonly used to open enrollment windows for Work/Life Events, but they can also be created manually by an administrator. The issue occurs when the Benefits Exception context does not provide a Deduction Start Date Rule.

The issue applies only when all of the following conditions are met:

• The benefit type is one of the following:
  • Insurance
  • Pension (excluding Savings Plan)
  • Deductible Allowance
• Payroll System is Employee Central Payroll(Integration Mode field in the benefit is set to Pay Components).
• The benefit deduction start date is configured as one of the following:
  • Always Next Pay Period
  • Next Pay Period Based on Paycheck Issue Date

In this scenario, the system incorrectly derives the deduction start date using the enrollment effective date instead of the configured deduction start date.

As a result, the Recurring Deduction and Recurring Information for Benefit Integration records are created or updated with an incorrect deduction start date. Since these integration records are consumed by Employee Central Payroll, the first payroll deduction may be scheduled earlier than intended.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental. 

SAP SuccessFactors Employee Central - Global Benefits

Issue occurs with one or more of the following:

• Recurring Deduction and Recurring Information for Benefit Integration records are created with an incorrect deduction start date.
• When an enrollment is modified, new Recurring Deduction and Recurring Information for Benefit Integration records are created using the enrollment change effective date instead of the next eligible deduction start date determined by the configured deduction start date.
• The first payroll deduction may start on the enrollment effective date instead of the next eligible pay period.
• Enrollment updates may fail with an integration error.

Scenario 1: New Enrollment Created Through Benefits Exception

Expected Behavior: When the benefit deduction start date is configured as Always Next Pay Period or Next Pay Period Based on Paycheck Issue Date, the deduction start date should be calculated according to the deduction start date setting in the Benefit.

For example, if an employee is paid semi-monthly and enrolls in a benefit during the current pay period, the deduction should begin in the next pay period.

Actual Behavior: If the Benefits Exception does not provide a Deduction Start Date Rule, the system calculates the deduction start date using the enrollment effective date instead of the configured deduction start date setting in the Benefit.

Impact

• The enrollment is saved successfully.
• No error is displayed.
• Recurring Deduction and Recurring Information for Benefit integration records are created with an incorrect deduction start date.

Because Employee Central Payroll consumes these integration records, the first payroll deduction may be processed earlier than intended.

Scenario 2: Enrollment Updated Through Benefits Exception

The impact depends on how the original enrollment was created.

Scenario 2A: Original Enrollment Created Through Benefits Exception

If the original enrollment was created through a Benefits Exception that did not provide a Deduction Start Date Rule, the associated Recurring Deduction and Recurring Information integration records already contain an incorrect deduction start date.

When the enrollment is updated through another Benefits Exception under the same conditions, the system continues to derive the deduction start date incorrectly.

Impact

• The enrollment update is completed successfully.
• No error is displayed.
• The existing Recurring Deduction and Recurring Information for Benefit integration records continue to contain the incorrect deduction start date.

As a result, the first payroll deduction continues to use the incorrect deduction start date.

Scenario 2B: Original Enrollment Created Through a Process That Calculated the Correct Deduction Start Date

Examples include:

• Benefit imports
• Standard enrollment processes
• Other enrollment processes that correctly derive the deduction start date

In these cases, the existing Recurring Deduction and Recurring Information for Benefit integration records already contain the correct deduction start date.

When the enrollment is later updated through a Benefits Exception that does not provide a Deduction Start Date Rule, the system creates new effective-dated Recurring Deduction and Recurring Information for Benefit Integration records using the enrollment change effective date instead of deriving the deduction start date according to the configured deduction start date setting in the Benefit.

Impact

• The enrollment update fails.
• The following error is displayed: Error BENEFITS_REC_INFO_INTG_SAVE_FAILED while saving Recurring Information for Benefit integration record.

The update attempts to overwrite an existing integration record with an incorrectly calculated deduction start date, resulting in a conflict.

Code correction will be performed for Benefits Exception processing to use the Deduction Start Date setting configured at the Benefit level when no Deduction Start Date Rule is provided in the Benefits Exception or Work/Life Event configuration. This ensures that Recurring Deduction and Recurring Information for Benefit Integration records are created and updated with the correct deduction start date.

Workaround:

To avoid this issue, configure a Deduction Start Date Rule in the associated Work/Life Event configuration used to create the Benefits Exception.

When a Deduction Start Date Rule is defined in the Work/Life Event configuration, the Benefits Exception uses that rule to derive the deduction start date. As a result, the Recurring Deduction and Recurring Information for Benefit Integration records are created with the correct deduction start date based on the configured rule.

If Benefits Exceptions are created manually, ensure that an appropriate Deduction Start Date Rule is provided so that the deduction start date is calculated correctly.

INC32103769, KI1H2026, Benefits Exception, Error, Incorrect start date, Deduction Start Date, Recurring Deduction, Recurring Information for Benefit Integration , KBA , LOD-SF-EC-GBF , Global Benefits , Known Error