roothr.ai
Blog

Payroll · · 6 min read

Can AI run payroll? What it should and should not do

A practical line between the parts of payroll an assistant can do well today and the parts that must stay with a person.

“Can AI run payroll?” is the question we get asked most, usually with a mix of hope and suspicion. The honest answer is: it can do most of the work, and it should do none of the deciding.

What an assistant does well

Payroll is mostly collection and arithmetic. Someone has to find out who started, who left, who was off sick, whose hours changed and whose salary was reviewed, then apply the right rules to each. That work is well suited to software that can read your HR records and knows the rules.

  • Collecting inputs. Starters, leavers, absence, overtime and rate changes are already in Root HR. The assistant reads them instead of asking you to re-key them.
  • Applying rules. Pro-rata for mid-month starters, SSP qualifying days, SMP rates, National Minimum Wage checks against age bands and hours.
  • Explaining differences. The most useful thing it does is list what changed since last month and why. That is what a good payroll clerk does before asking you to sign.
  • Producing outputs. Payslips, the FPS and journal entries, generated on approval.

What must stay with a person

  • Approving the run. A named person reads the changes and approves. This is not a formality; it is the control.
  • Judgement calls. Whether a bonus is contractual, whether an overpayment is recovered this month or next, whether a leaver is owed notice pay. The assistant can lay out the options with the rule behind each one, but it should not choose.
  • Anything it is unsure about. If a record is missing or contradictory, the right behaviour is to stop and ask, not to guess.

How we built roothr.ai around that line

Every payroll answer comes with three things: the figures, the list of changes and the source record for each change. The approve button is a real approval step that is logged with who clicked it and when. If the assistant cannot resolve something, the run is marked as blocked with a plain description of what is missing.

Payroll should take ten minutes of reading and one decision, not a week of assembly. The reading and the decision are yours.

If you want to see what a prepared run looks like on your own data, book a walkthrough.

Try it on your own Root HR data

We are onboarding early access teams in small groups.

Get early access