HR Document Flow
Payroll run Validate / Process / Approve / Post and related HR document statuses.
HR Document Flow
HR payroll runs expose a row Actions menu with Validate → Process → Approve → Post. Related entities use their own status enums.
Hub: Target Document Flow. Overview: HR & Payroll.
Payroll runs
UI Actions (Payroll Runs grid — always listed; server enforces order):
| Action (UI) | Purpose |
|---|---|
| Validate | Validate run data |
| Process | Process calculation |
| Approve | Approve for posting |
| Post | Post to payroll / GL path |
Filter UI may use free-text status such as Posted for posted runs.
Payroll run — Validate through Post
flowchart TB Start((Create)) --> Draft[Draft] Draft -->|Validate| Validated[Validated] Validated -->|Process| Completed[Completed] Completed -->|Approve| Approved[Approved] Approved -->|Post| Posted[Posted] class Start egkStart class Draft egkDraft class Validated,Completed egkActive class Approved egkSuccess class Posted egkTerminal
Related HR statuses
| Document | Statuses |
|---|---|
| Payslip | Generated, Sent, Viewed |
| Leave encashment | Pending, Approved, Rejected, Paid |
| Insurance claim | Submitted, UnderReview, Approved, Rejected, Paid |
| Application | Applied, Screening, Interview, Offer, Hired, Rejected |
| Onboarding task | Pending, InProgress, Completed, Skipped |
#Post-action sync
After Validate / Process / Approve / Post, the payroll runs grid reloads. Failed steps show errors without advancing.
#Scenarios
| Scenario | Result |
|---|---|
| Successful post | Run appears as posted |
| Approve before process | Server rejection / no advance |
| Reject leave encashment | Status Rejected |