EnglishOperating ScenariosHR & payrollOverview

HR & payroll

Common operating scenarios for HR & payroll. Each page answers: what to do, why, the steps and what to avoid.

ScenarioShort answer
Leave spanning the new yearSubmit one request; the system splits the balance across both years.
Self-service leave turned offHR files the request on their behalf at /hr/leave.
Picking Leave in the request catalogThe system opens the Leave form; no Employee Request is created.
New employee cannot use self-serviceHR links the User to the Employee first.
Employee cannot see the payslipWait for Payroll to move the run to approved/paid.
Clocking in on the webOnly when web_attendance_clock is on; otherwise use mobile.
Attendance device not sending dataConfigure the device and key before receiving punches.
Employee leaves the companyTerminate — pending Leave is cancelled, the User deactivated and the offboarding checklist opened.
From Job Requisition to active employeeApprove Job Requisition → Opening → Hire (pre_onboarding) → checklist → probation approval → active.
Logged OT missing from the payslipCreate an OT request from the log, approve it, recompute the draft run.
OT approved by mistakeNot yet in payroll: Unapprove, then reject with a reason.
Overnight OT end time errorEnter HH:MM in company time — the system treats it as overnight (240 minutes).
Manager cannot click Approve on an OT requestHand it to a superior or adjust the hours.
Payroll run refused: unknown formula variableOpen Payroll Inputs, read the red cell, fix the Salary structure formula or enable the feature that supplies the variable.
Payroll blocked by completion evaluationApprove that employee’s evaluation, or (by company decision) turn off the block to use the default value.
Full days despite many absencesA workday cell marked Default means no attendance at all in the period — check devices or create an adjustment.
Punch on an approved leave dayDecide: cancel the leave (the employee worked) or keep the leave and exclude the punch.
Employee missing from the payroll runCreate a salary profile (base salary + structure).
Voiding a run that has a supplementary payrollVoid the supplementary run first, or correct via arrears/clawback.
Approving time: by week or by line?Managers approve the week at /time-tracking/approve; PMs approve lines when T&M billing is needed.
Editing time in a locked periodDo not edit time; adjust with a finance document or in the next period.
Gap between attendance and logged hoursUse Unified time to chase missing logs; never auto-create an Invoice.
Hiring an individual freelancer with PIT withholdingIndividual Contact → lump-sum contract → tax profile → Payment run → approval → pay.
Locking attendance before payrollClear Default workday cells, punches on leave days and OT requests before creating the run; consider requiring attendance confirmation.
Paying casual and seasonal workersTurn on Workforce Management and set seasonal/casual employment type with the contract pay_basis; outside freelancers use the individual service channel.
Paying by completionUse the completion_pct variable in the Salary structure formula, sourced from the approved completion evaluation.