Leave that is requested by email and tracked in Excel wears HR down and corrupts the timesheet. In the Leave Management module the employee requests leave from their phone and the manager approves their team's requests from a single queue; the moment a request is approved, the leave is posted to the timesheet as "On leave" and stays in sync with the leave records in SAP/ERP. Who is off, when, and on which leave type — the answer is always in one place and always current.
In SAP, Microsoft Dynamics 365, NetSuite or Odoo, leave is a record that feeds the payroll calculation — an employee opening a request from their phone, a manager seeing and approving their team's requests, approved leave landing on the timesheet the same day, and HR viewing leave analytics by type, month and department is not what the ERP does. So in practice the process runs on email, WhatsApp and Excel sheets; leave is keyed into the ERP days later and never matches the timesheet. The Leave Management module closes that loop in the portal: request, approval, timesheet and ERP sync become one flow, and the ERP remains the single source of truth.
The employee opens a request from the native mobile app (Sanctum-token API), picking the leave type, the start and end dates and a reason; the number of days is calculated automatically from the date range. They follow their own request history and status (pending/approved/rejected) on the same screen.
Leave types are defined freely in your company's own terminology; for companies running SAP, type names come straight from SAP's absence-type description texts (T554T). Annual leave, sick leave and unpaid leave are classified automatically for reporting, with the paid/unpaid breakdown ready out of the box.
Approval authority follows the organisation hierarchy: each manager sees and approves only the requests of their own direct reports, while HR-level roles see the whole company. Approvals and rejections take a single tap - with a reason note on rejection - from the web approval centre or the mobile approval screen.
The moment leave is approved, every working day in the range is posted to the Time & Attendance timesheet grid as an "On leave" row - a day not worked never shows up as an absence. Public holidays and weekly rest days are skipped intelligently; days with actual punches and locked timesheet rows are never overwritten.
Absence/leave records in SAP (PA2001) are imported idempotently against a unique record key: however many times the sync runs, no duplicates are created. Leave arriving from the ERP is tagged "SAP-sourced" and requests opened in the portal are tagged "manual" - the two worlds never blur into each other.
When leave days are posted, the company- and location-level public and religious holiday calendar and the weekly rest days in the employee's shift plan are both taken into account. For an employee taking Friday to Monday off, the weekend is never written to the timesheet as leave days; the timesheet stays true to reality.
A scheduled job syncs approved leave with the timesheet every morning over a rolling 60-day forward window; the Time & Attendance day close also posts the closing day's leave and reports how many leave days were written. An authorized manager can still mark a day as "On leave" by hand when needed.
Total leave-day KPIs; breakdowns by type, month and department; year-over-year trend and seasonality charts - all ready on the HR dashboard. Which department empties out in summer, which month sick leave peaks in - you plan with data instead of guesswork.
Every request records who approved or rejected it, when, and with which note; even deleted records leave a trace (soft delete). Approval screens are protected by permission-based access: employees see only their own requests, managers only their own team.
Leave type, date range and reason are selected; the day count is calculated automatically and the request lands in the manager's queue as "pending". No email, no paper form.
From the web approval centre or the mobile approval screen, the manager sees the pending leave of their own team and approves with a single tap - or rejects with a reason note.
Approved leave shows as "On leave" in the timesheet grid and the attendance reports; the HR dashboard updates its leave analytics by type, month and department. Nobody has to ask "where are they today?".
At the moment of approval and in the automatic sync every morning, the working days in the leave range are posted to the timesheet; holidays and weekly rest days are skipped, worked days and locked rows are preserved.
Leave records in SAP/ERP are synced without duplicates; leave days travel to payroll inside the approved and locked monthly timesheet from Time & Attendance. Leave data is never entered twice.
Leave Management mirrors the leave and personnel records in your ERP read-only; the single concrete output produced in the portal - approved leave days - travels to payroll through the timesheet. The ERP remains the single source of truth; the portal takes on the request-approve-track layer.
SAP's absence/leave records (PA2001) and its leave-type description texts (T554T) are pulled into the portal on a regular sync. Because every record is matched on a unique key, re-running the sync never creates duplicates; ERP-sourced records are mirrored with approved status and never pushed through the approval flow.
Leave approved in the portal is posted to the Time & Attendance timesheet as "On leave" days; at month close the approved and locked timesheet goes to the ERP with the payroll export. A draft or pending request never flows to the ERP - only the approved, finalised result is written.
For companies without a SAP/ERP connection, requests are opened and approved entirely inside the portal, with personnel data managed via Excel import. The native mobile app and the web approval centre share the same leave core; there is no per-user licence.
Tell us your ERP and your process. We’ll show how this module works and scope it into your subscription — no man-day, licence or setup fee.
Book a Demo →