Loading
Module
Payroll in OneclickHR has a review step. You see the run — every line, every breakdown — before anything is finalized. Pay schedules, overtime rules and currency are configured once in your workspace and applied every cycle.
What this solves
Payroll is the one process where a mistake costs real money and real trust. An employee underpaid by a hundred dollars does not file a bug report; they lose confidence in the company. An employee overpaid has to be asked to give money back, which is worse.
Most of these mistakes are not calculation errors. They are input errors — a wrong hours total, an overtime rule that did not apply, a currency that got assumed. The calculation was right; it was fed the wrong thing. Which is why the single most useful feature in a payroll module is not the math. It is the moment before the math becomes final.
OneclickHR puts a review step in front of every run. Nothing finalizes until you have looked at it.
What is included
Build a run, read it, then finalize it. The review is a stage in the process, not an optional report you have to remember to open.
Set the cadence your organization actually pays on in workspace settings, and runs follow it rather than assuming a monthly cycle.
Overtime policy lives in workspace settings and applies to the hours recorded in attendance and timesheets, so the rule is written down once instead of applied from memory.
Pay people in the currency they are paid in. Salary figures and payslips carry their currency rather than defaulting to one and hoping.
Each payslip shows its components rather than a single net figure, so an employee asking "why is this number what it is" has an answer on the document itself.
A standard format, and a US-style format carrying the fields a US payslip is expected to carry. Pick the one that matches where the employee is paid.
Payslip documents you already have can be read automatically to pull the figures out, so moving historical pay data in does not mean retyping it line by line.
Payslips land in the employee’s own portal. They do not have to email anyone to get a copy of a document about their own pay.
A payroll run reads the hours recorded in attendance and the hours submitted on timesheets, applies the overtime policy configured in your workspace, and uses the salary and currency on the employee record. Every one of those inputs is visible before you finalize, which is the point of the review step: when a line looks wrong, you can follow it back to the day it came from.
Because attendance days are computed in your organization’s timezone, the hours a run consumes belong to the days you think they belong to. This is not a detail. A shift that drifted into the wrong calendar day is the most common cause of a payroll figure nobody can explain.
Finalized payslips go to the employee’s self-service portal as PDFs, carrying your brand color, in whichever of the two formats you chose.
Payroll shares its records with the rest of the workspace, so these modules read the same data rather than a copy of it.
Sign your organization up, configure your timezone and brand color, and invite your team. You can be running the same day.