Most disputes between a company and its employees don't start from bad faith, but from three numbers the two sides don't agree on: how much was actually worked, how much leave remains, and what is owed when the relationship ends.
Those three share one property: they are all cumulative. They aren't calculated once but built day by day — which is precisely why manual calculation fails at them.
Number One: Worked Hours
Recording attendance isn't an end in itself; it is an input to three decisions: deductions for absence and lateness, overtime calculation, and proof of compliance in any challenge.
What the system should track automatically:
- Actual clock-in and clock-out times, not scheduled ones.
- Lateness and early departure with a grace period adjustable to your policy.
- Overtime separated between working days and holidays — their rates usually differ.
- Different shifts if you run more than one work pattern.
The most important condition in this module is that the record cannot be edited silently. Any correction must be logged with who made it, when, and why — because a record that can be changed without a trace serves neither you nor the employee as evidence.
Number Two: Leave Balance
Leave isn't a number of days but a running account: it increases with monthly accrual, decreases with use, may partly carry forward to the next year, and whatever remains is paid out at end of service.
And leave types don't behave alike:
| Type | Effect on pay | Effect on balance |
|---|---|---|
| Annual | Paid | Deducted from balance |
| Sick | Per your country's law and its duration | A separate balance |
| Unpaid | Deducted at the actual daily rate | Not deducted from annual |
| Emergency / other | Per your policy | Defined by your internal rules |
Confusing the first and third types is the most common error: unpaid leave recorded as annual, so the balance is reduced and the pay isn't — or the reverse.
Important note: leave entitlements and carry-forward rules differ across Gulf countries and are set by each country's labour law. Configure the rules in your system to match your own country's law, and check with the competent authority on any update.
Number Three: End-of-Service Entitlements
This number appears only once — the day an employee leaves — but it accrues from their hire date. Companies that calculate it only at maturity face two problems at once: a surprise hit to cash, and books that had been showing profits higher than reality.
What the system should track:
- Length of service calculated from the hire date to the day.
- The wage the benefit is calculated on — basic or gross, per your country's law.
- Unused leave balance payable in cash.
- The monthly accruing provision, recorded in accounting as it builds.
- Any other obligations: repatriation ticket, notice pay, outstanding advances to deduct.
The fourth item separates a company that knows its obligations from one that discovers them. The calculation rules themselves differ by each country's labour law and are updated from time to time — so check the text in force in your country rather than relying on any system's default setting.
How these numbers flow into the monthly run is detailed in the payroll guide, and recording the end-of-service provision in accounting is covered in the integration article.
Why Manual Calculation Fails at All Three
Not because the arithmetic is hard — but because the three numbers are cumulative and interlinked: attendance feeds pay, leave feeds both the balance and pay, and the balance feeds end-of-service entitlements.
Any error in one link surfaces months later in another — when tracing its source is hard. And that is exactly what makes a dispute with an employee intractable: nobody can prove where the figure came from.
What an Employee Portal Ends
When employees see their own attendance record, leave balance, and payslip, most of the discussion ends before it begins. The bigger effect isn't saved management time — it is that disagreement shifts from an argument over memory to a review of a shared record.
Frequently Asked Questions
Why must attendance be linked to payroll?
Because deductions and overtime are built on attendance data. When the record sits apart from the payroll run, figures move by hand — so the error appears while its source doesn't, and every deduction becomes disputable.
What is the difference between unpaid and annual leave in calculation?
Annual is paid and reduces the balance. Unpaid is deducted from pay at the actual daily rate and doesn't reduce the annual balance. Confusing the two is among the most repeated errors in manual calculation.
How are end-of-service benefits calculated?
The rule differs by each Gulf country's labour law, in both service length and the wage used. Check the text in force in your country and configure your system to it rather than relying on a default setting.
Why should the end-of-service provision be recorded monthly?
Because it is a liability accruing from the hire date. Not recording it makes profits look higher than they are, then the full amount lands at once on the day it falls due — straining cash at a time you didn't plan for.
Does leave balance carry forward to the next year?
It depends on your country's law and your written policy. What matters is that the rule is single, configured in the system, and known to the employee — because ambiguity here becomes a claim at end of service.
What is the fastest improvement to apply?
Giving employees access to their own leave balance and payslip. It ends the most repeated questions to management and turns any later disagreement into a record review instead of an argument from memory.
Conclusion
The three numbers — hours, balance, and entitlements — aren't administrative detail. They are the employment relationship itself translated into figures. A company that can evidence each with a record never enters a dispute in the first place.
Pick one member of your team and ask: what is their leave balance right now, and what would they be owed if they left tomorrow? If it takes more than a minute, those numbers are being calculated outside your system.