India
Seven days, paid in full by the employer.
The employer, at full pay.
Casual leave is a separate seven days again, with its own balance and its own approval route.
Leave and absence
Somebody asks for a week. The weekend inside it is not leave, and neither is the public holiday — but only if the system knows which country's calendar that person is measured against. Ours does, before the request is opened.
Read from the statutory tables in the product on 15 October 2026. Add a country and its set arrives with it.
The question behind the policy
Three countries, the same absence, three different answers — and in two of them the answer changes partway through the week. This is the part a leave policy copied from a template gets wrong, and the part a spreadsheet cannot hold.
India
Seven days, paid in full by the employer.
The employer, at full pay.
Casual leave is a separate seven days again, with its own balance and its own approval route.
Cyprus
Three days on you, then the fund.
The employer.
The Social Insurance Fund, not you.
Nothing is payable until the person has six months of service.
Greece
Half pay first, then EFKA.
The employer, at half salary.
The social insurance institution.
How long it runs depends on length of service, so there is no single annual figure to quote — and we do not invent one.
These are the statutory defaults the product ships with, not legal advice. Your own policy sits on top of them and can be more generous in any direction.
The request
An employee sees what they have, what they have taken and what is left before they ask. Whoever decides sees the same figures, and what saying yes would leave behind.
Day one
A new company is not set up with an empty leave screen and a link to the handbook. It arrives with the statutory types for its country already there, with the right number of days, the right carry-forward rule and the right answer about who pays. Then you change whatever you want.
India
Cyprus
Greece
Before you ask
Yes, and a half day is charged as half a day against the balance rather than rounded up. Where a company charges a half day for a late arrival, that lands in the same place and comes out of the same entitlement.
Carry-forward is set per leave type, with a cap where you want one — India's earned leave ships with a cap of forty-five days because that is what the law contemplates, and Cyprus ships with none. What is carried is recorded as its own line, so next year's balance can be explained rather than just asserted.
The person who wrote it, their manager and an administrator. Not the rest of the company, and not a colleague looking at the team calendar — they see that somebody is away, not why. That is enforced in the database rather than by what a screen chooses to display.
No. One account, with each company's own holidays, working week and leave types. Someone moving between them keeps one record, and is measured against the calendar of wherever they now sit.
We import them from a spreadsheet and show you the before and after rather than inventing a starting point. A leave balance that is wrong by two days is worse than no system at all, so this is the step we spend the most time on.
Bring the awkward one
The messier it is, the more useful the half hour. We would rather find the rule we cannot model while you are still deciding than after you have moved everybody onto it.
Things people bring us