Leave and service missions: moving beyond the paper trail

The paper trail has one virtue: everyone understands it. It also has a major flaw: information stops at the last desk that received the form. The leave is granted, but attendance counts it as an absence; the mission is over, but the per diem is still waiting.

Leave, from request to balance

• The employee submits the request online, from their phone, and sees their balance.
• Their manager approves it, or rejects it with a reason, following the workflow defined for the entity.
• Once approved, the leave covers the corresponding absences: they drop out of the anomalies.
• The balance updates at the same moment, and payroll takes it into account.

The service mission, from order to reimbursement

The mission order is created and approved in the platform. During the mission, the employee is not “absent”: their attendance is covered. On return, the mission report, per diem and expenses to reimburse are attached to the same record. Nothing is re-entered between the department that sends and the one that pays.

Rules specific to each entity

Leave types, annual entitlements, approval workflows, per diem scales: each department, campus or subsidiary has its own. In a multi-entity organisation, these rules coexist without mixing — see Multi-entity.

And for the employee?

They know where their request stands, they know their balance, they download their payslips. Trust in the system also comes from there: the employee sees the same data as HR.

Leave and missions feed directly into payroll calculation. That is the whole point of a single record.