Skip to content

HR & Payroll

Each employee record tracks status (Active, Inactive, Terminated, On Leave, Probation) and employment type (Full Time, Part Time, Contract, Temporary, Intern, Consultant) — driving what shows up in payroll runs and leave eligibility rather than being purely informational fields.

  • Attendance records clock-in/out or daily attendance status per employee.
  • Leave applications cover a full range of leave types — Annual, Sick, Maternity, Paternity, Personal, Bereavement, Educational, Emergency, and Unpaid — each going through its own application/approval flow before it affects attendance or payroll.
  • Payroll runs — process pay for a group of employees (a payees list) together for a given period, rather than one employee at a time.
  • Payslips — the per-employee output of a run, itemizing pay components and deductions.
  • Payroll posts real Accounting journal entries — a payroll run is a ledger event, not just a generated PDF.

Employee benefits (health, retirement, allowances, and similar) are tracked per employee, separate from base payroll, so total compensation isn’t hidden inside a single payroll number.

Structured reviews tied to an employee record, giving a running history of review cycles rather than a one-off document.

The most granular section of HR — training has its own sub-model:

  • Training programs, each with a budget and tracked expenses against it.
  • Sessions under a program, with participants enrolled per session.
  • Providers — the external or internal source delivering the training.

This lets a training budget be tracked against actual spend across many sessions and providers, not just a single line item.

See also: Users & Permissions — an HR employee record (a person on payroll) is a separate concept from an Orbit user (a login with a role), since not every employee needs system access.