Payslip Lifecycle & Approval

Updated 31 May 2026

Overview

Why it matters: Pay should not go from draft to bank without review. A formal lifecycle (draft → lock → approve → paid) separates preparation, control, and execution, and can freeze amounts once paid for audit.

Extra actions such as Year End Unused Leaves help close the year without leaving entitlements unclear.

Status flow

Fields Table

Payslip status (field on the form)

Header actions (buttons)

Field labels explained

Payslip status

Stored state driving which buttons appear; only forward moves when policy allows (e.g. cannot Approve from Draft without Lock if that is your rule).

Recalculate

Re-runs payroll computations from current master data—use after any change to time, salary, or tax inputs.

Days Calculation

Opens the day-by-day view or wizard tied to this payslip period.

Lock

Signals “ready for review”; often restricts edits to approvers only.

Approve

Formal approval before payment—may map to a second signer in your process.

Paid

Confirms disbursement; may persist frozen values for audits.

Year End Unused Leaves

Informational or adjustment action for leave balances—depends on module configuration.

Related

See Generate Payslips, Payslip Days Review, and Payslip Report (PDF).

Common mistakes

Payslip Lifecycle & Approval