Skip to main content
Upikajob Demo

Leave & Absence: Absences that follow your workflow

For HR administrators and managers: every absence request goes through your approval workflow, with balances set to your rules.

Book a demo Try an example

Leave & Absence

One request, one workflow, one status.

Illustration: a period selected in the calendar, the request and its approval workflow, the updated balance and the request history.

An example request workflow. The applicable rules must be defined with your organization.

Try it yourself

Submit a leave request

Choose a period and a unit, then send the request: it stays pending until the approver has decided.

Leave request · Léa Moreau

Paid leave

No supporting document required for this type

WorkflowWith approver

1Period, in June

First day, then last day. Weekends, grayed out, cannot be selected in the example.

2Allowed unit

Choose the first day of the absence, then the last: the request’s duration appears here.

See this case with your organization

Leave & Absence day to day

What the module handles

Absence request

Submit a request based on the options enabled.

Configurable workflow

Distinguish declared absences from requests that need approval.

Request history

Find statuses and cancellation options.

Before you start

Getting started with Leave & Absence

The rollout

  1. Configure

    Define types, units, balances and approvers.

  2. Test

    Compare the calculations with your rules on representative cases.

  3. Launch and support

    Explain requests, decisions and balance corrections.

  1. From request to status

    The employee chooses an active absence type, a period and a unit, with a supporting document if the type requires one, then tracks the request.

  2. Check the rules before opening the module

    Balances, units and deduction rules must reflect your policies: test them on representative cases (half days, public holidays, different calendars).

    Check any balance that differs from your HR or payroll records before opening the module to all.

    • Enabled absence types and supporting documents.
    • Deduction rules and opening balances.
    • Approvers and team scopes.
    • Cancellation conditions and corrections.

  3. Prepare the link with timesheets

    If both modules are enabled, leave is integrated into timesheets: check that units and approved absences match.

In the demo

Prepare your demo

The demo starts from your organization and a fictitious use case: no employee records are needed.

What we review

  • Centralized requests
  • Identified statuses and approvers
  • A history available within the authorized scope
Book a demo
Upikat AI A question to prepare for your demo: “Are your half days and public holidays counted the same way as in your payroll?” Message written by the Upikajob team. Upikat is the AI assistant that helps prepare reviews.

Helpful answers

Your questions, simply answered.

Pointers to assess your project and prepare the right questions.

All questions
Can we use several absence types?

Yes: each enabled type has its own units, mode (declared or subject to approval) and any supporting documents.

Is the balance necessarily identical to the payroll balance?

Not necessarily: check the initial data, accrual and deduction rules, and data exchanges between tools. It is better to examine a discrepancy than to promise synchronization.

Can an approved request be canceled?

It depends on the setup and the start date: an approved request that has already started can’t be canceled; corrections go through the person in charge.

Your next step

Let’s start from how your teams really work.

Your sites, your reviews, your priorities. Prepare a demo built around the use cases that matter to your organization.

Book a demo Understand pricing
EN