In this article
Who is this feature for?
Any company that records employment end dates — for leavers working their notice, fixed-term contracts, or seasonal staff.
What was wrong?
If an employee had an employment end date set, they could still book leave for dates after it. Leave Dates accepted the request without complaint.
The result was leave sitting in the calendar for days when the person was no longer employed: deducted from an allowance they no longer had, showing up in reports, and quietly distorting the final figures at exactly the moment you need those figures to be right.
Requesting TOIL beyond an end date was already blocked correctly. Ordinary leave wasn't. We fixed that inconsistency.
How does it work?
There's nothing to configure. If an employment end date is set on someone's record, any leave request covering dates after that day is now rejected, with the same error message TOIL has always shown.
This applies to everyone, whatever their role. An admin booking leave on a leaver's behalf meets the same wall the employee does.
The start of the employment period was already enforced, so leave now has to sit inside the employment period at both ends.
Employees without an end date are unaffected, which is almost everybody, almost all of the time.
What about leave that's already booked?
Nothing already in the system is touched. This stops new requests being made outside someone's employment period; it doesn't go back and tidy up anything that slipped through before the fix.
So if you've been setting employment end dates for a while, it's worth checking whether anyone has leave still sitting after their last day. Those bookings are still there, and still counted.