Build a pay run from attendance and time tracking, add bonuses, mark it Paid, and the Salaries entry lands in the general ledger by itself. It is a pay register, not a statutory payroll service, and this page says so plainly.
Included from Pro upwards
"Load active employees" auto-builds a payslip for every active employee: hours from time tracking, days from attendance, gross computed by their pay type.
Tag bonuses and add custom disbursements per payslip, on top of the automatically loaded figures.
Marking a run Processed or Paid creates a Salaries ledger entry automatically through a database trigger, in the same transaction as the status change.
The ledger entry is keyed to that specific payroll run, so re-processing a run cannot double-post it.
If you run more than one entity, the Company scope bar filters payroll, attendance and the ledger to one company at a time, same as every other finance page.
The part you would otherwise find out in week three. If one of these is central to how you work, raise it before you buy rather than after.
No. This is a pay register: gross pay comes from salary, hours or attendance, and an admin types in the deductions. There is no statutory tax calculation and no filings, so it is not a replacement for a payroll provider on that front.
No. There is no direct deposit. A run gives you the payslip figures and the accounting entry; the transfer to each employee still happens through your bank, the same as before.
Yes. Marking a run Processed or Paid posts a Salaries entry to the general ledger by itself, and re-processing the same run never posts it a second time.
Yes. The Company scope bar that covers the rest of finance covers payroll too, so each entity’s run and its ledger entry stay separate.
The full product documentation for this module is at /docs/hr.
Free for up to 5 seats, no card required. Every module is in the same workspace, so nothing needs connecting to anything.