Managing leave well is one of the highest-leverage habits a growing company can build. In Sri Lanka, teams juggle annual leave, casual leave, medical leave and company holidays, often across more than one site, while managers and payroll still need the same numbers.
This is an operations guide from Syncora (Pvt) Ltd, the Colombo company that builds Staffora. It is not legal advice. Entitlements depend on the contract, the sector and the statute that applies to that employee. Confirm the policy with a qualified adviser, then put the policy you have actually adopted into a system people will use.
Start with a written policy
Write each leave type down before you buy software. For every type, record the entitlement, whether it accrues, whether it carries forward, who can approve it, and what evidence is required. Ambiguity here creates most of the friction between staff and managers.
Most organisations need at least:
- Annual leave — planned time off, often accruing with tenure
- Casual or short leave — shorter absences with lighter notice
- Medical leave — supported by the policy and, where you require it, documentation
- Half-day leave — the same approval path as a full day, or the calendar will lie
- Special leave — maternity, paternity, compassionate or other categories your policy names
If two managers can approve the same day in two different chats, you do not have a policy yet. You have a habit.
Approvals that still work when you grow
A single approver is fine while the company is small. It fails when that person is travelling or when HR must see certain types before they hit a balance. Multi-level approval — reporting manager, then HR — keeps control without blocking people, as long as the path is the same for half-days and full days.
Decide what happens when the approver is the person on leave. Name a delegate in the policy, not in a WhatsApp message on the morning of the request.
One holiday calendar
Public holidays in Sri Lanka should live in one calendar that leave balances respect. When the calendar is wrong, every roster and every report downstream is wrong. Give the calendar an owner, review it each year, and show it to staff. Do not keep a second list in a spreadsheet "just in case".
What employees and managers should see
Employees should see their balance and request leave without emailing a file. Managers need a simple view of who is away. HR needs an export for planning and for the conversation with payroll. That loop — request, approve, balance, report — is the core of leave operations.
Self-service only works if the balance on screen matches the policy. If the software cannot express a rule you use, fix the configuration or change the policy. Do not ask people to ignore the number.
Where software helps, and where it does not
Staffora is Syncora's HR workspace. It includes leave types, policies, multi-level approval, a holiday calendar, half-day support and reports, alongside employee records and attendance. Pricing is listed in LKR on that site. Payroll is not part of the live product.
Software will not decide your legal entitlement. It will stop the same day being approved twice, and it will show a balance that follows the rules you entered. If you are formalising leave for the first time, write the policy, confirm it, then put that policy into the product.
A short rollout
- 01Name an owner for the policy and the holiday calendar.
- 02List leave types, balances and approvers.
- 03Load employees and opening balances. Check a sample by hand.
- 04Ask one team to use it for a fortnight before you switch the whole company.
- 05Keep the old spreadsheet read-only until the sample matches.
If the sample does not match, do not go further. The failure is in the rules or the opening numbers, and a bigger rollout will only spread it.