3755271 - EmpTimeAccountBalance OData API returns incorrect balance when using a future-dated balanceAsOfDate

When querying time account balances using the EmpTimeAccountBalance entity, the system calculates incorrect or unexpected values if the balanceAsOfDate parameter is set to a future date.

• balanceAsOfDate in the past: Correct results are returned.
• balanceAsOfDate omitted (defaults to today's date): Correct results are returned.
• balanceAsOfDate in the future: Incorrect or incomplete results are returned.

Sample Request: GET https://api10preview.sapsf.com/odata/v2/EmpTimeAccountBalance?$format=json&balanceAsOfDate=2026-05-31&$filter=userId in '123456'

• SAP SuccessFactors Employee Central
  • OData API

This behavior occurs because accrual simulation is not supported for the EmpTimeAccountBalance OData API entity.

While the SuccessFactors User Interface (UI) can dynamically simulate future accruals (e.g., projecting daily accruals forward to a date like May 31st based on the Time Account Type configuration), the OData API does not replicate this simulation logic. The OData API only calculates balances based on existing, hard-posted transactions up to that date, ignoring any unposted future simulations.

Because this is a known limitation of the OData API framework for this entity, you must use an alternative API endpoint if you require simulated future balances

Utilize the dedicated REST API: Time Account Balances instead of the OData API. The REST API endpoint natively supports the calculation and simulation of future-dated balances exactly as seen on the Administer Time UI.

EmpTimeAccountBalance, balanceAsOfDate, future date, incorrect balance, OData API, simulation, accrual simulation, SuccessFactors, Time Off, REST API, Time Account Balances , KBA , LOD-SF-INT-EC , Employee Central SFAPI & OData Entities , Problem