Symptom
The effective_end_date filter is not correctly applied for segments paycompensation_non_recurring and deduction_non_recurring.
The records with a pay_date/deductionDate before the effective_end_date are returned in the response, which is incorrect.
Environment
- SAP SuccessFactors HCM Suite
- Compound Employee API
Resolution
Current behavior:
- Using effective_end_date >= "date" returns records with dates earlier than the filter.
- Using effective_end_date = "date" returns all possible records.
- This is not the intended behavior.
During February 2026, a patch was applied in the following dates to fix the behavior:
- Preview: Feb 24th, 2026
- Production: Feb 26th, 2026
However, these patches caused issues in integrations that were expecting the previous behavior. So, the patches were rolled back in Production and Preview environments.
Now, the SuccessFactors Engineering is planning to implement a solution in 1H 2026 to fix the issues which will change the behavior to:
- With effective_end_date >= "date", earlier records should no longer be returned.
- With effective_end_date = "date", all possible records will be returned (the same behavior from before).
- A new SFAPI parameter named "applyEffectiveEndDateFilterToKeyDateBasedSegments=true" will be implemented, which can be used in combination with effective_end_date = "date" and will result in only the key-date based records for the provided effective_end_date to be returned.
The following segments will be affected by this change:
- paycompensation_non_recurring
- deduction_non_recurring
- BenefitsIntegrationOneTimeInfo
This new behavior will be documented in the Compound Employee API implementation guide and also in the What's New Viewer pages during the release dates, so there can be proper timing for testing.
See Also
- SAP SuccessFactors Product Release & Road Map Information
- SAP SuccessFactors Patches Knowledge Base
- KB Article 2171560 - How to be notified of new or updated SAP Notes or KBAs
Keywords
SAP Knowledge Base Article - Public