Skip to main content

Record leave and suspension status

ON_LEAVE and SUSPENDED record the employee's current administrative state. They require a current employment and employee status-management authority. They are not attendance or leave-request workflows.

  1. Confirm the approved decision and reason through the organisation's process.
  2. Review the current employment and any intended pay/benefit implications separately.
  3. Reload employee detail, choose Change status and select ON_LEAVE or SUSPENDED.
  4. Enter the reason and save.
  5. Verify status history and separately handle login access if required.
  6. On return, review current employment and use an explicit ACTIVE status change with a reason.

What the action does not calculate​

There are no leave balances, request approvals, absence-day records, accrual rules or automatic return dates in this status action. It does not prorate salary, suspend insurance, approve overtime or freeze an account.

Example: Amira goes ON_LEAVE for an approved period. Her compensation record remains the agreement until an authorised separate change. A Payroll preparer cannot infer unpaid days solely from this current status; Payroll's own input rules and approved quantities are separate.

An operational integration that requires a currently ACTIVE employee may reject someone ON_LEAVE or SUSPENDED, while the HR record remains readable under its normal scope. That does not mean their login was disabled or that every module uses identical active-employee rules.

Recovery and evidence​

If employment is future-dated or already ended, the requested state is refused. Keep the actual dates accurate and arrange the appropriate HR decision. If a return action is attempted before a valid rehire period exists, establish that period first.

Record only necessary information in the status reason; do not paste medical details or confidential case evidence into a broadly read employment-history reason. A status event retains the administrative transition, not a full leave case file.

No scheduled process automatically returns the employee to ACTIVE. Assign the follow-up to the responsible team and verify the actual saved status on return.