Aller au contenu
ERPStack

Flux de travail RH

Leave Management

Leave requests, balances, holidays, policy settings, approvals, calendars, imports, and workforce availability evidence.

Implémenté Evidence-first module page
Primary users
Employee Department manager HR manager Payroll officer
/app/leave/management
Visuel derive de l application
Leave management workspace
Open app route
Demandes
Approval routed
Balances
Tracked
Imports
Validated
Domaine Statut Preuve
Demandes Manager reviewed Decision trail
Balances Policy aware Adjustment proof
Calendrier Team visible Availability view

Workflows clés

What the module helps operators complete.

Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.

Step 1
Submit and approve leave requests
Step 2
Review team calendars and leave balances
Step 3
Manage leave types, holidays, and policy settings
Step 4
Import balances and report workforce availability

Feature checklist

Capabilities grouped the way operators look for them.

3 capability groups

Leave request flow

  • Employee requests
  • Manager decisions
  • Cancellation
  • Amendment

Leave administration

  • Leave types
  • Holiday calendar
  • Balance adjustments
  • Carry forward

Leave reporting

  • Team calendar
  • Balance report
  • Import evidence
  • Policy visibility

Carte des modules connectes

How this module exchanges business context with the rest of ERPStack.

Module Relation
RH Employee profiles, departments, and managers
Workflow Leave approvals, cancellation, and amendment routing
Paie Leave balances and payroll-period context
BI Absence, balance, and workforce availability reporting

Governance and reporting

Controls and management visibility expected from a serious ERP module.

Gouvernance
  • Policy-gated approvals
  • Balance adjustment audit
  • Import validation
  • Manager decision evidence
Rapports
  • Leave calendar
  • Balance report
  • Leave usage
  • Policy exceptions

AI coverage policy

What ERPStack can honestly claim for this module today.

AI claims are tied to the official Agent Tool Registry, evaluation evidence, safe-mode controls, and scheduled-agent monitor readiness. Roadmap modules only show planned coverage until module-native tools are implemented.

AI L3 ready
Coverage claim Current AI coverage: Leave L3/L3 ready through the official Agent Tool Registry.
Governance evidence Governance evidence: 5 registered tools, 7 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence.
Scheduled monitor Scheduled monitor readiness: not in the current proactive-agent monitor wave.
L4/L5 boundary Remaining L4/L5 gap: no autonomous execution or self-optimizing agent behavior is claimed; write paths remain permissioned, previewed, and confirmable.

Evidence-first standard

Module pages explain value, workflow, control, and proof in one place.

This page structure supports the current public module catalog with app-derived visuals, connected-module evidence, governance proof, and report context that can be compared against real product routes.

Feature clarity

Buyers can see concrete function groups instead of vague capability claims.

Operational fit

Workflows, users, and connected modules show where the module belongs.

Governance proof

RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.

Review path

Public pages link back to app routes so reviewers can compare page claims to product surfaces.