Before you start
Put the right records and roles in place.
Each employee needs a Salary Assignment effective for the month, and a Contribution Scheme must exist for the run's year. The 2026 scheme ships pre-seeded; verify its values against the year's budget acts before your first live run. The person who posts runs belongs in the Approver group.
Documented sequence
From the salary register to the posted run.
Each stage identifies the action, handoff, or record change that moves the work forward.
- 01
Keep the salary register — Payroll officer
A raise is a new Salary Assignment row with a later valid-from date, never an edit of the old one. The salary for a month is the employee's newest row on or before it, so the table keeps the full history.
- 02
Record the month's amounts — Payroll officer
Add one Payroll Entry per bonus, overtime, allowance, deduction or advance, with the month, a positive amount and a reason. The entry type decides whether it adds or subtracts and whether it is taxable.
- 03
Create the run — Payroll officer
Create a Payroll Run for the month. It starts as DRAFT and at once computes one read-only payslip per employee with an effective salary: base, swept entries, insurable income, contributions, income tax, gross, net and employer cost.
- 04
Review the totals — Payroll officer
The run's totals add up from the payslips. If a figure is wrong, fix the assignment or the entries, have the run rejected and create a new one; payslips are never edited.
- 05
Post or reject — Approver
The approver opens the Post task in the Inbox. Post makes the run POSTED, final and read-only; Reject releases the swept entries, removes the payslips and sets the run to CANCELLED.
Connected work
Carry the record into the next decision.
Related features and workflows reuse the same business records instead of asking teams to rebuild the context.
A posted run cannot be edited; a mistake is corrected in the next month's run or through entries in a new run.
A starting point, not a fixed package
Match the run to your pay rules.
Entry types, with their direction and taxability, and the per-year contribution schemes and rates are maintained in the settings as data. Other pay components or approval steps can be scoped as a Custom adaptation.
Try BusinessIntentsDecision-stage answers
Run the monthly payroll FAQs
Where do the contribution and tax rates come from?
From the Contribution Scheme for the run's year, kept as data in the settings. The shipped 2026 values are a starting point to verify against the year's budget acts; a run for a year without a scheme fails with a message naming the year.
How do I recalculate a run?
Fix the salary assignment or the entries, have the run rejected and create a new one. Rejecting releases the swept entries, so the next run picks them up again.
Can employees see their payslips?
Yes. Once a run is posted, each employee opens My Payslips in the Personal workspace and sees only their own payslips, read-only, with every fiche line.
Can a run be posted without payslips?
No. Posting is refused when the run computed no payslips, which usually means no salary assignment was effective for that month.
Review the real workflow
Walk one real payroll month through BusinessIntents.
Use a real record or transaction to compare the documented flow with the way your team works today.