Skip to main content
Question

Absence Limit negative carry over ?

  • March 13, 2026
  • 2 replies
  • 15 views
K
Sidekick (Partner)
Forum|alt.badge.img+6

Hello everyone,

We use APP10 / Aurena. 

In 2025, we defined an absence limit for an absence type. The 2025 ANNLV reduction of 29 hours was intentional as Kallum sold 29 hours annual leave at the end of the year. We manually adjust the absence parameter for everyone that sells annual leave. Therefore the 2025 ANNLV limit is correct with 156 hours. 

Hower, the reduction of 29 hours should only affect the 2025 limit and not the 2026 limit. I don’t want those 29 unused hours to be carried over. But it’s the case, the hours for 2026 should be 17+26. 

The absence group configuration does not allow carry-over as the “Carry Forward Absence Type” field is empty.


The root cause of the issue is that the -29 hours limit unused is automatically carried over to the 2026 limit… 

How can we ensure that this negative balance is not carried over to the following year? 

2 replies

K
Sidekick (Partner)
Forum|alt.badge.img+6
  • ksebf
  • Author
  • Sidekick (Partner)
  • March 16, 2026

Does anyone know? 

jbush0419
Do Gooder (Customer)
Forum|alt.badge.img+3
  • jbush0419
  • Do Gooder (Customer)
  • March 19, 2026

​@ksebf -

it looks like you're encountering the “negative carryover functionality” in IFS, which is designed to reduce future year allocations when employees have taken excess leave in previous periods. However, in your case, the -29 hours represents sold leave (not excess taken), so it shouldn't impact the following year.

I’ve not done this, but what comes to mind is instead of reducing the 2025 limit directly, you could:

  • Keep the full 185 hours for 2025
  • Create a separate absence registration for the 29 sold hours (perhaps with a specific absence type for "sold leave")
  • This way the system won't see it as unused negative balance to carry forward

The key is ensuring IFS doesn't interpret the sold hours as "excess taken" that needs to be recovered in subsequent years.

not sure if this will solve your issue, but it’s what I would try.  Hope that helps

 

-jason

Terms & ConditionsCookie settingsAccessibility statement