Overtime request flow
- Yêu cầu
- Attendance candidates
- Manager decisions
- Cancellation
Quy trình nhân sự
Overtime
Overtime requests, attendance candidates, rate policies, approval routing, reports, and payroll handoff readiness.
Đã triển khai
Evidence-first module page
Primary users
Employee
Supervisor
HR manager
Payroll officer
App-derived visual
Overtime management workspace
Yêu cầu
Workflow routed
Rates
Policy controlled
Lương
Handoff ready
| Khu vực | Trang thai | Bằng chứng |
|---|---|---|
| Candidates | Attendance sourced | Worked-time proof |
| Phê duyệt | Manager decision | Workflow trail |
| Rates | Policy applied | Rate evidence |
Quy trình chính
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
Create overtime requests from attendance candidates
Step 2
Review overtime against rate policy and schedule context
Step 3
Approve, reject, and report overtime pressure
Step 4
Prepare payroll-ready overtime evidence
Feature checklist
Capabilities grouped the way operators look for them.
Rate policy
- Rate tables
- Policy settings
- Eligibility checks
- Exception review
Overtime reporting
- Employee report
- Management report
- Pressure view
- Payroll handoff
Connected module map
How this module exchanges business context with the rest of ERPStack.
| Module | Quan hệ |
|---|---|
| Attendance | Attendance candidates and worked-time evidence |
| Lương | Approved overtime pay inputs and reconciliation |
| Workflow | Approval routing and decision history |
| BI | Overtime pressure and labor-cost reporting |
Governance and reporting
Controls and management visibility expected from a serious ERP module.
Quản trị
- Approval routing
- Rate policy controls
- Attendance-source evidence
- Payroll handoff audit
Bao cao
- Overtime requests
- Overtime pressure
- Rate usage
- Payroll readiness
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: OT L3/L3 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 4 registered tools, 6 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.