Payroll execution
- ก่อนหน้า
- Runs
- สลิปเงินเดือน
- Adjustments
ไม่พบการเชื่อมต่ออินเทอร์เน็ต
กำลังพยายามเชื่อมต่อใหม่
เกิดข้อผิดพลาด!
กำลังพยายามเชื่อมต่อใหม่
บุคลากร
Payroll periods, runs, payslips, payments, bank files, reconciliation, statutory packs, settings, and accounting handoff evidence.
| พื้นที่ | สถานะ | หลักฐาน |
|---|---|---|
| Runs | Period scoped | Approval proof |
| Payments | Bank-file ready | Provider evidence |
| Reconciliation | Accounting linked | Close handoff |
เวิร์กโฟลว์หลัก
Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.
Feature checklist
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 |
Controls and management visibility expected from a serious ERP module.
AI coverage policy
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
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.
Buyers can see concrete function groups instead of vague capability claims.
Workflows, users, and connected modules show where the module belongs.
RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.
Public pages link back to app routes so reviewers can compare page claims to product surfaces.