An unnoticed overtime miscalculation often surfaces at payroll. With the 1H 2026 Release, SAP has introduced a change to the default logic in SAP SuccessFactors Time Tracking 2026 that appears to be a simplification at first glance: attendances and absences can now coexist without the system throwing an error. In this article, we explain what that means in practice, and why a configuration adjustment is essential in most cases.

What has changed?

Previously, overlapping attendance and absence entries would typically trigger an error message and be blocked at system level. With the 1H 2026 Release, this behavior can now be configured. Depending on the chosen configuration, attendance and absence entries can exist in parallel. This adds flexibility to the system, but it also increases the importance of having the right valuation logic in place.

At first glance, this change looks like a simplification. In practice, however, a critical gap emerges when the valuation logic is not adjusted accordingly.

Why does it matter?

When attendance and absence times overlap, both entries are stored independently. Without the appropriate valuation logic, the overlapping period is not automatically neutralized. This can lead to incorrect overtime calculations, as work time and absence may both feed into the overtime logic simultaneously.

This is relevant in the following scenarios:

• Employee works in the morning and takes leave in the afternoon
• Sick leave is recorded after attendance has already been captured
• Shift models with complex overtime evaluation
• Retroactive changes to attendance or absence entries

How do you prevent incorrect overtime in SAP SuccessFactors Time Tracking 2026?

To ensure correct overtime calculation, the overlapping period between attendance and absence must be explicitly removed from the overtime calculation. Since SAP does not automatically account for this overlap under the new default behavior, a dedicated Time Valuation is required.

First, a Deduction Valuation identifies the period during which attendance and absence overlap. The result is stored in a separate Time Type Group. This Time Type Group is then used as a negative input in the Overtime Valuation, effectively deducting the overlapping period from the work time relevant for overtime.

Conclusion

The change to Collision Handling increases system flexibility, but simultaneously shifts the functional responsibility to the Time and Valuation configuration. New standard functionality does not automatically mean correct time evaluation, what matters is the design of the underlying logic.

​Unsure whether your SuccessFactors system is configured correctly? At Clarity Solutions, we help organizations identify configuration gaps, build the right foundation, and future-proof their SAP SuccessFactors landscape through consulting, tailored solutions, and long-term support.

Contact

Quelle: SAP SuccessFactors Release Information 1H 2026