Payroll execution
- 이전
- Runs
- 급여명세서
- Adjustments
인력 워크플로
급여
Payroll periods, runs, payslips, payments, bank files, reconciliation, statutory packs, settings, and accounting handoff evidence.
구현됨
Evidence-first module page
Primary users
Payroll officer
Finance manager
HR manager
Employee
App-derived visual
Payroll operations workspace
Runs
Approval aware
Bank files
Provider ready
회계
Close linked
| 영역 | 상태 | 증거 |
|---|---|---|
| Runs | Period scoped | Approval proof |
| Payments | Bank-file ready | Provider evidence |
| Reconciliation | Accounting linked | Close handoff |
핵심 워크플로
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
Prepare payroll periods and runs
Step 2
Review payslips, adjustments, and approvals
Step 3
Generate bank files and payment batches
Step 4
Reconcile payroll with accounting and year-end evidence
Feature checklist
Capabilities grouped the way operators look for them.
Payment control
- Payment batches
- Bank files
- Provider readiness
- Reconciliation
Statutory evidence
- 설정
- Year-end documents
- Accounting handoff
- Export controls
Connected module map
How this module exchanges business context with the rest of ERPStack.
| Module | 관계 |
|---|---|
| 인사 | Employee identity, compensation, and sensitive records |
| Attendance | Worked time, corrections, locks, and shift context |
| Leave / Overtime | Approved absence and overtime pay inputs |
| 회계 | Payroll journal, payment, and reconciliation evidence |
Governance and reporting
Controls and management visibility expected from a serious ERP module.
거버넌스
- Payment approval
- Bank-file provider evidence
- Unauthorized export controls
- Accounting close handoff
보고서
- Payroll runs
- 급여명세서
- Payment reconciliation
- Year-end evidence
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: Payroll L3/L3 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 8 registered tools, 9 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.