Scheduling an end of service
An employee resigns today and their last working day is a month away. You go to record the decision, and suddenly they cannot clock in, cannot take leave, cannot even log in — while they still work for you for another full month. That is not a data-entry mistake. That is a system that does not understand that a decision can have a date other than the day it was entered.
The idea in a minute
Recording a decision is one thing; applying it is another. Zemam separates the two: the decision is recorded now, and it takes effect on its own day.
How it works
- 1
1. You record the decision with its date
You set the last working day and the reason — resignation, contract end, termination by the company, or another reason you write out. The decision is recorded on the contract immediately, so the contract honestly says when it ends and why.
- 2
2. And the employee carries on working
Until that date the employee is like anyone else: they clock in and out, they take leave if they are owed it, they log in, and they are paid in the month's payroll normally. Because they are, quite simply, still working — which is exactly what should happen.
- 3
3. The system ends it on the day
On the date itself the system applies the termination by itself: the contract closes and the employee moves to ended. Nobody needs to remember or come back and press a button, and nobody is left with a login still working two months after they left.
- 4
4. It happens in your company's own time
“Today” is judged in your company's own timezone, not the server's. So the last working day ends at the end of the day where you are, rather than a few hours' difference ending someone's employment a day before they finish work.
- 5
5. Today or a past date applies immediately
If the employee actually left today or a few days ago, it applies at once with no waiting. Deferral is only for future dates — so the ordinary case gains no extra complexity.
- 6
6. Things the system refuses, to protect you
A termination date cannot be earlier than the contract's start. A reason of “other” cannot be chosen without writing the detail. And a leave-balance payout cannot be scheduled in advance — it is a real money event dated the day it happens, so the system tells you to do it on the day or settle it separately, rather than accepting the request and silently dropping part of it.
In short
You record the decision today and it takes effect on its own date — the two are not the same thing.
Attendance, leave, login and payroll all keep working normally until the last day.
It applies automatically on the day, in your own timezone — nobody has to remember.
The reason is recorded, and the decision is documented with who entered it and when.
Situations that happen
A resignation with a month's notice
The most common case. The employee works the full month and hands over. Recording the decision early lets management plan a replacement without disabling someone who is still working.
A fixed-term contract nearing its end
A contract ending in December that you have decided not to renew. You record the decision with its reason now, and the employee serves their full term.
An agreed end date
An agreement to end employment on a specific date. The agreement is recorded with its date and reason, so there is no later dispute about when the last day was.
A move to another branch or entity
The current contract ends on a date and a new one starts after it. Separating the decision from its effect keeps the transition clean, with no gap day.
Recording an end of service and disabling the employee by mistake?
Talk to us and we'll show you how the decision is recorded now and takes effect on its own day, with nobody disabled early.