People & payroll

Employees, salary history, leave, attendance, and pay runs that post into the ledger.

Book a demo · See all modules

What you get

Who runs this

Questions

Do pay runs hit the general ledger? Yes — accrual journals post to expense, tax, social security, and net payable.

Draft → post → pay → void follows the same money rules as the rest of the workspace. Posted LCY journals keep payroll beside the books instead of in a separate spreadsheet.

Can salaries use a second currency? Yes — optional secondary salary currency with LCY conversion.

Effective-dated salary history can store a secondary currency. The pay run converts to local currency so journals stay balanced in LCY.

What if we void a posted run? Posted or paid runs reverse with balancing journals.

A reversing void keeps the audit trail. You do not delete history to fix a mistake — you reverse and re-run when needed.

Is leave and attendance included? Yes — leave, holidays, attendance, equipment, and contracts sit beside payroll.

Day-to-day HR ops live in the same People module so the team that runs payroll can also mark attendance and track equipment without another product.

Are roles isolated from company finance? Yes — HR access does not imply ledger or cash access.

People & payroll permissions stay separate from company finance. An HR manager does not see available cash or the P&L unless an admin grants finance pages.

Can we export bank payment files? Yes — bank CSV export and employee payslips from the pay run.

After posting, pay the run, export the bank file your payroll bank expects, and issue payslips from the same screen.

What this does not do

Connected to the rest of the system

FAQ

Can salaries use a second currency?

Salary history supports an optional secondary salary currency with LCY conversion on the pay run.

What if we void a posted run?

Posted or paid runs reverse with balancing journals so the books stay correct.