Skip to content
ERPStack

Workforce workflow

HR / Payroll

Workforce records, leave, attendance, overtime, payroll periods, payslips, approvals, and payment controls.

Implemented Evidence-first module page
Primary users
HR manager Payroll officer Department manager Employee
/app/hr/employees
App-derived visual
Workforce operations console
Open app route
Identity
Role scoped
Payroll
Approval gated
Export
Audited
Area Status Evidence
Employees Directory + records Sensitive change audit
Attendance Correction flow Approval trail
Payroll Payment review Reconciliation proof

Core workflows

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
Maintain employees, departments, and positions
Step 2
Approve leave, attendance correction, and overtime requests
Step 3
Run payroll periods and payslip review
Step 4
Control sensitive exports and payment approval

Feature checklist

Capabilities grouped the way operators look for them.

3 capability groups

Workforce records

  • Employee directory
  • Departments
  • Positions
  • Sensitive records

Time and policy

  • Leave
  • Attendance
  • Corrections
  • Overtime

Payroll operations

  • Previous
  • Runs
  • Payslips
  • Payment approval

Connected module map

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

Module Relationship
Accounting Payroll postings and reconciliation evidence
Workflow Leave, attendance, overtime, and payroll approvals
Security Operations Sensitive change and unauthorized export visibility
BI Headcount, attendance, payroll, and workforce analytics

Governance and reporting

Controls and management visibility expected from a serious ERP module.

Governance
  • Sensitive-change SIEM events
  • Payroll payment approval
  • Role-gated exports
  • Audit trail
Reports
  • Headcount
  • Attendance
  • Leave balance
  • Payroll reconciliation

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 coverage ready
Coverage claim Current AI coverage: HR L3/L3 ready; Payroll L3/L3 ready through the official Agent Tool Registry.
Governance evidence Governance evidence: 15 registered tools, 20 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence.
Scheduled monitor Scheduled monitor readiness: 1/1 ready (Payroll Payment Approval Monitor).
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.