The company's list of days off: one row per day, with the name of the day, whether it is paid, and optionally the branch it applies to.
When to use it
- After generating a year's holidays from the festival catalogue, to check the result and add the days the catalogue does not know about, such as a company anniversary or a local strike day.
- To extend a festival that is generated as one day but observed over several.
Before you start
You need create rights on this screen. Generate Holidays checks the same rights, because it writes into this list. If you are going to generate the year, do that before adding days by hand, so a re-run does not land on top of your edits.
Where to find it
Setup > Calendar Setup > Holiday.
The fields on this screen
| Field (on screen) | What to enter | Required |
|---|---|---|
| Holiday Date | The day the office is closed. Enter one row per day, so a festival of several days needs several rows. | Yes |
| Holiday Name | Name of the day off, such as Dashain. It is filled in for you when you sync from the festival calendar. | Yes |
| Type | public / optional / restricted | No |
| Paid | (not explained yet) | No |
| Branch | Limit this holiday to one branch. Leave it blank when the whole company is closed that day. | No |
| Notes | (not explained yet) | No |
| Festival (optional) | Link to Festival Master; auto-fills date from the festival catalog | No |
How it works
Rows get here in two ways: you add them, or Generate Holidays builds them from the festival catalogue for a Nepali year. A generated row carries the festival it came from. A later re-run matches on that link when you ask it to refresh existing days.
On a generated row, the festival decides the Type and the Paid tick, not you. A festival marked as a national holiday produces a paid public day, and any other festival produces an unpaid optional day. You can change either afterwards, but running the generation again with the refresh option puts them back.
One row is one day. A festival observed over five days needs five rows. Generation produces one day per festival, so you always add the extra days here.
Leaving Branch empty means the whole company is closed that day. Naming a branch limits the day off to that branch.
Know where this list stops before you rely on it:
- Attendance sheets are not marked from it. When a period's attendance is worked out, days come out as present, leave, weekly off or absent. A day is only marked as a holiday if someone sets it on the sheet. Adding a day here does not stop it counting against an employee.
- The calendar in the application does not take its days from here. The festivals and the Nepali calendar you see elsewhere come from the calendar built into the product.
Treat this as the company's record of its own days off, and set the attendance sheet to match when the time comes.
Tips and common mistakes
- Generate the year first, then add by hand. Done the other way round, a later refresh overwrites the rows that came from a festival and leaves duplicates of the ones that did not.
- Watch for two rows on the same day when a company day you added later turns out to be a festival too. Nothing here prevents it.
- Use the Notes box to say why a non-festival day is off. Nobody remembers a year later.
Related guides
See also Generate Holidays, Festival Master, Festival Year Override and Attendance.