Leave management for small companies works when three things are true: every request is submitted and approved in one place, balances update automatically from those approvals, and the result reaches payroll without anyone re-typing it. WhatsApp messages and an Excel sheet fail all three, which is why small teams end up with disputed balances, two people off on the same day and unpaid leave that never gets deducted. This article shows what the simplest adequate system looks like, how to move to it in about a week, and how to avoid turning it into bureaucracy.
Why WhatsApp and Excel stop working
For a five-person team, a message to the boss and a note in a sheet is fine. The breakdown comes gradually:
- A request is approved in a chat and never reaches the sheet, so the balance is wrong.
- Two staff in the same role are both approved for Eid week because neither approver saw the other request.
- The sheet has a formula error from two years ago and nobody knows which balances are right.
- An employee resigns and disputes their unused leave in the final settlement, and the only evidence is a chat history.
- Unpaid leave is forgotten at payroll and the overpayment is never recovered.
None of these is a people problem. They are the predictable result of storing approvals in one place and balances in another. The signs are the same as the ones that tell you to leave spreadsheets for a CRM; see CRM vs Excel: 7 signs it is time to switch.
What a simple leave system must have
Leave types and rules
Annual, sick, unpaid, public holidays and the family-related types your staff are entitled to under the Labour Law (see mohre.gov.ae for the current entitlements). Each type has an accrual rule, whether it is paid, whether a document is needed, and whether it carries over.
Balances that calculate themselves
An opening balance per employee, monthly accrual, deductions on approval, and adjustments with a reason. The employee can see the number at any time.
Request and approval flow
Employee submits from their phone, the supervisor approves or rejects with a comment, and a second approver is added for longer absences if you want. Everyone involved gets a notification. The employee self-service portal is where this lives for staff.
Team calendar
Who is off when, visible to the team without personal details, with a warning when too many people in one role are away at once.
Payroll link
Unpaid days reduce salary automatically; leave balances feed the final settlement when someone leaves.
Reports
Balances by employee, leave taken by month, upcoming absences, and a liability figure for unused leave.
What you do not need yet
Small companies sometimes buy more than they can run. Skip these until you have a reason:
- Complex multi-level approval matrices. One approver plus an optional second is enough.
- Automatic policy enforcement for every edge case. Let a human decide the rare ones and record the reason.
- Integration with calendars across three platforms. A team calendar inside the HR app is enough to start.
Switching in about a week
| Day | Task | Who |
|---|---|---|
| 1 | List leave types, accrual rules and approvers | Owner / admin |
| 2 | Reconcile each employee's current balance and get it agreed | Admin with each employee |
| 3 | Set up the system: employees, types, opening balances, approvers | Admin, vendor support |
| 4 | Train supervisors to approve on their phones | Admin |
| 5 | Announce to staff, install the app, submit first requests | Everyone |
| Month-end | Check unpaid leave reached payroll correctly | Admin / accountant |
Day 2 is where the time goes, and it is worth it. Every future balance builds on the opening figure, so have each person confirm it in writing inside the system.
Keeping it light
- Make submitting a request faster than sending a message. Two taps and a date range.
- Approve within a day. If managers sit on requests, people revert to asking in person.
- Publish public holidays at the start of the year so the system knows them.
- Review balances with each employee once a year so there are no surprises at exit.
- Use the reports to spot patterns, such as frequent Monday sick leave, and handle them as a manager, not through the software.
When leave sits inside the same system as attendance and payroll, the month-end job becomes a review rather than a reconstruction. That matters more now that wages are due on the 1st of the following month under Ministerial Resolution No. 340 of 2026 and warnings can begin on day 2 of delay. For the full picture of how leave fits with attendance, payroll and WPS, read HR and payroll software for UAE companies.
Frequently asked questions
How many leave types should a small company set up?
Start with the types your contracts and the law actually provide: annual, sick, unpaid, public holiday, and the statutory family-related types that apply to your staff. Add compensatory off if you give time in lieu for overtime. Avoid creating a type for every situation; a note field on the request handles the rare cases.
Who should approve leave in a company with no HR department?
The direct supervisor approves, and the owner or admin is copied or has a second-level approval for longer absences or sensitive periods. The important thing is that the approval happens in the system, not in a chat, so that the balance, the calendar and payroll all update from one action.
What happens to leave balances when we switch systems?
You enter the opening balance for each employee as at the go-live date, after reconciling it with the employee. From then on the system accrues and deducts automatically. Getting this opening figure agreed with each person is the single most important step, because every future balance builds on it.
Does leave data need to connect to payroll?
Yes. Unpaid leave must reduce salary, and leave balances are part of any final settlement. If the leave tool is separate from payroll, someone has to transfer the figures by hand every month, and with wages due on the 1st of the following month under Resolution 340 of 2026 that is a step you want to eliminate.
Can staff see each other's leave?
They should see a team calendar showing who is away, without reasons or personal details, so they can plan handovers. Managers see their team's requests and balances. Only HR and the owner see the full picture. Role-based access makes this straightforward in any proper system.
How Zaini Developers can help
The leave module in StaffManager Pro covers types, accruals, approvals, a team calendar and the payroll link, with an employee app in English, Arabic, Hindi, Urdu and more. For a small company we keep the setup to what you need and help you reconcile opening balances so day one is clean. It is part of our wider HR and business software, and you can try the request-and-approve flow in the live demo. Contact us to get started.