Skip to content
Absence· an app for Microsoft 365

Absence: Leave approved in one click.
And everyone sees their own balance.

An employee requests time off, an approver decides in one click and the approved absence appears in the team calendar straight away — and at the end of the month the payroll summary is ready.

Who it's for Companies that handle leave by e-mail and spreadsheet annual leave, sick days, home office and doctor's visits
What it costs from €75 per month per company, by number of users
Deployment Implementation €220 one-off the app creates its lists and permissions itself

Runs in your Microsoft 365 — no foreign cloud, no extra passwords.

Book a demo
How it works

Three steps anyone can manage.

The whole process fits in one paragraph — and your people will find it just as easy.

  1. The employee requests time off

    Picks the type and dates — a half day too, or a time from–to for a doctor's visit. The app counts working days without weekends and public holidays.

    The balance shows on the overview straight away
  2. The approver decides

    Approvers get an e-mail about the new request and decide from the queue in one click. A rejection always carries a reason.

    The requester gets the outcome by e-mail
  3. The team and payroll stay informed

    The approved absence is in the team calendar straight away. At the end of the month an administrator downloads the payroll summary as a CSV.

    Sensitive types only as “Absence”
Inside the app

What it looks like in practice

Balances on the overview, a new leave request with an instant summary of days, the team calendar and approving a request with one click.

What changes

Today vs. with Absence

This is how it looks in many companies for as long as leave runs through e-mail and a spreadsheet.

Today “People ask for leave by e-mail. Who approved it?”One writes to their manager, another in a chat, a third stops by in person. The approval stays in someone's mailbox.
With the app One request, one decisionThe approver decides from the queue in one click and the approved absence is in the team calendar straight away.
Today “How much leave do I have left?”HR searches the spreadsheet and works out the half days. Few people know who is away next week.
With the app The balance at a glanceEntitlement, carry-over, days taken and pending requests — and the overview shows who is away today, this week or this month.
Today “At the end of the month I retype absences for payroll.”The overview is pieced together from e-mails, notes and calendars. One overlooked request and the numbers no longer add up.
With the app Payroll summary in one clickA person × absence type table with totals as a CSV for Excel — approved requests only, and the app warns about pending ones.
The fastest route

30 minutes on screen, no company presentation

  • 5 minHow people ask for time off today and who approves what
  • 10 minA request, balances and the team calendar through an employee's eyes
  • 10 minApprovals, entitlements and the payroll summary through a manager's and HR's eyes
  • 5 minWhat a rollout would mean for you + pricing
Pick a demo slot → Free and with no commitment · online in Teams
11 areas — click one for details

Time-off requests

Absence type, dates and, for a single day, a half day. For a multi-day absence you can take a half day at the start and at the end — if you still work in the morning or come back in the afternoon on the last day. Hour-based types, such as a doctor's visit, take a time from–to. The app counts the working days without weekends and public holidays; an overlap with another of your own requests only raises a warning, the approver decides. One request can last at most a year — a longer absence is entered as several consecutive requests.

A link straight to a new request

A link on the intranet, in an e-mail or in a step of the Life Situations Centre can open the new request form directly — with the type already selected, annual leave for example. If the type from the link does not exist in the app, the form selects no other type and asks you to choose, so nobody sends the wrong kind of absence by mistake.

Balances and editing requests

For annual leave: entitlement, carry-over from last year, days taken and, separately, what awaits approval; for sick days: entitlement, days taken and pending. Leave over New Year is deducted from the balances of both years — each year gets only the days that fall into it. Requesters can edit a pending request themselves and cancel a pending request or an approved absence that has not started yet.

One-click approvals

A queue of pending requests with dates, number of days and the note, a badge with the count in the menu and search that ignores diacritics. A rejection requires a reason, which the requester sees on the request and in the e-mail. Approvers are e-mailed about every new request and the requester about the decision — always through Microsoft 365, from the account of whoever took the action.

Team calendar

A monthly people × days view with approved absences, weekends and public holidays; an absence that spans two months shows in both. The home screen shows who is away today, this week or this month.

Sensitive types protected in the data

Types marked as sensitive go into the shared calendar only as a neutral “Absence” entry — an hour-based absence, such as a doctor's visit, even without the time or number of days. The real type is not stored there, so it cannot be found even by querying outside the app. The default types sick leave, sick day and doctor's visit are sensitive from the start; when you create a type with such a name yourself, sensitivity is pre-filled and an administrator can switch it off. It can be switched on for any type.

Private requests

The request list has item-level permissions: an employee can reach only their own requests in SharePoint, approvers and administrators can reach all of them. The note stays with the request.

Entitlements and people

An administrator enters employees' annual entitlement to leave and sick days and the leave carried over from last year, and sees what everyone has taken and has left. Statutory calculations and reductions stay in your payroll system.

Payroll summary

A monthly table of person × absence type with totals per person and for the company on screen, and a CSV export for Excel: for each employee the days per type, total days and total hours. Filters for month, year and a specific employee apply to the export too. Only approved requests are included; the app warns about pending ones. An absence that spans two months or two years is split by days — each month gets only the days that fall into it.

Absence types, holidays and roles

One button in Settings adds eight common types — annual leave, sick day, sick leave, home office, doctor's visit, business trip, time off in lieu and unpaid leave; types you already have stay as they are. Further types you add yourself, with an allowance (annual leave, sick days or none), a unit (days or hours), a colour and a sensitivity flag. Czech public holidays for a chosen year, Easter included, are added in one click; company days off you add yourself. Employee, approver and administrator roles can be given to individuals or to whole Entra ID groups.

Teams and phone

Absence runs as a team tab and as a personal app in Microsoft Teams. On a phone it offers a simplified view for a quick request or approval.
Area
EP365 Absence
E-mail and spreadsheets
Forms and Power Automate
Cloud HR system
Data inside your Microsoft 365
yes, entirely
files and mailboxes
yes
someone else's cloud
Leave balance at a glance
entitlement, carry-over, taken
by hand in a spreadsheet
has to be built
yes
Working days without weekends and holidays
counted by the app, half days too
by hand
has to be built
yes
Approval with a rejection reason
yes, in the e-mail too
a reply in the e-mail
depends on the flow
yes
Team calendar masking sensitive types
sensitive types as “Absence”
whoever has the file sees it all
has to be set up
depends on the product
Payroll summary
CSV per month
retyped by hand
export from a list
yes
Statutory entitlement and reductions
no — HR enters it
by hand
no
usually yes
Deployment
implementation for €220
straight away
building and tuning flows
rolling out a new system

Your data stays with you

Requests, entitlements, absence types, holidays and the team calendar live in SharePoint lists on the app's site inside your Microsoft 365, under your identities and permissions. The app has no server or database of its own and uses no AI.

Requests private in the data too

The request list has item-level permissions: an ordinary employee can reach only their own requests in SharePoint, approvers and administrators can reach all of them. This is not hiding in the app — someone else's request is out of reach even with a direct link.

Sensitive reasons masked on write

For types marked as sensitive the shared team calendar gets only a neutral “Absence” entry. The real type is not there at all, so it cannot be found even by querying outside the app. The note on a request never reaches the calendar, e-mails or the payroll summary.

Only administrators change the setup

Absence types, holidays and annual entitlements are protected by SharePoint permissions — only the app's administrator group can write them, while everyone who uses the app can read them. The app's settings are protected the same way.

No new passwords

People sign in with their company Microsoft account, and e-mails go out through Microsoft 365 from the account of whoever took the action. When someone leaves, IT handles it in one step — blocking the account removes access to the app too.

Only the licence request reaches us

The app downloads the file with your company identifier and expiry date and checks it in your browser. The app sends us no requests, names or reasons for absence; the app code, fonts and release notes load from our content delivery network. A bug report or suggestion reaches us by e-mail only when a user sends it.

Licence

Monthly licence by company size

Up to 25 M365 users
€75 / month
26–70 M365 users
€125 / month
71–150 M365 users
€175 / month
More than 150 M365 users
Individual

The subscription is based on the total number of internal users in your Microsoft 365. Within a given size you get the full scope of the app, with no surcharges for individual features.

Deployment

Implementation

€220 one-off

The app creates its lists, role groups and the permissions on the request list by itself the first time a site administrator opens it. Together with you we then set up absence types, public holidays, annual entitlements, approvers and roles — and you are ready to go.

What we need from you

A site administrator to open the app for the first time, and a one-off approval of the app's Microsoft Graph permissions in the SharePoint admin centre — the app requests them all at once. Without them it sends no e-mails and does not recognise roles given to Entra ID groups. A group is notified only at its own e-mail address, and annual entitlements are entered for people added to a role individually.

Extended support

Support rate

€110 / hour

Consultancy, environment changes, training or user support beyond the licence.

How we calculate support

Support is charged per each started 15 minutes of work. We always tell you the expected scope up front.

Prices exclude VAT
Does the app calculate the statutory leave entitlement?
No. HR enters the annual entitlement to leave and sick days, and the app tracks what is taken and what is left. Leave reductions and statutory calculations stay in your payroll system — EP365 Absence is not a payroll, time-and-attendance or HR information system.
Will colleagues see that I'm at the doctor's or off sick?
No, as long as the type is sensitive. The default types sick leave, sick day and doctor's visit are sensitive from the start, and when you create a type with such a name yourself, sensitivity is pre-filled — an administrator can switch it off. For other types it is one tick in Settings. The team calendar then gets only a neutral “Absence” entry, without the time for a doctor's visit, and the note stays with the request. The real type is visible to you, the approvers and the app's administrators.
Who approves a request?
The approvers you set in Settings — individual colleagues or a whole Entra ID group — and the app's administrators. There is a single approval round, and an approver sees all pending requests in the company, not only their own team's. Automatic routing to a line manager, delegation and multi-level approval are not available yet.
How do absences get into payroll?
An administrator picks a month — and optionally a year or a specific employee — and downloads the payroll summary as a CSV for Excel: for each employee the days per type, total days and total hours. It contains only approved absences matching the on-screen filter; the app warns about pending requests. An absence that spans two months or two years is split by days: leave from 29 September to 3 October counts in the September summary only with its September days and in the October summary with its October days. There is no direct link to a specific payroll program yet.
How long can one request be?
A year at most — a longer absence is entered as several consecutive requests. A request over the turn of a month or a year is fine: the team calendar shows it in both months, the payroll summary splits it by days, and leave over New Year is deducted from the balances of both years.
Does the app put leave into Outlook?
Not yet. Who is away and when is shown by the team calendar and the overview in the app.
Does it work in Teams and on a phone?
Yes. Absence runs as a team tab and as a personal app in Microsoft Teams, and on a phone it offers a simplified view for a quick request or approval.
Where is our data stored?
In your Microsoft 365, in SharePoint lists on the app's site. Only the licence request reaches us — the app downloads the file with your company identifier and expiry date and checks it in your browser. The app uses no AI and no server of its own.
Is the interface in English?
Not yet — the app's interface is in Czech and the one-click public holidays follow the Czech calendar. The names of absence types and company days off are up to you.
What does deployment involve and what does implementation cost?
Implementation is a one-off €220. You add the app to your Microsoft 365 and a site administrator opens it for the first time — it creates its lists, role groups and the permissions on the request list by itself. Together with you we then set up absence types, public holidays, annual entitlements, approvers and roles. If you want to try it out first, sample data is created in Settings in one click.
How do app updates work?
You upload the package to your App Catalog just once. New versions then load on their own and your admin manages them right inside the app — on the Version management card in Settings they can pin a version or roll back to an earlier one. No repeated package deployments: we ship improvements continuously — without a pinned version your site gets them automatically, with a pinned version you switch when you choose.