The agent stages payroll changes; it never commits them. It reads approved records from the HR system, prepares each change as a pending input in payroll with its effective date and any back pay calculated, and a payroll specialist approves the batch. Bank detail changes, one-off payments and anything sourced from an email are held.
What counts as a payroll change, and who owns it?
Payroll changes are the inputs that differ from last period: new starters, leavers, salary changes, allowances, deductions, overtime, sickness and parental pay, tax code notices from the tax authority and changes to pension contributions. Each has an owner upstream. HR approves a pay rise; a manager approves overtime; the employee changes their own bank details, which then need verification.
The payroll manager owns the payroll: what enters it, the calculation, the run and the final sign-off before payment. In many organisations a second person in finance approves the net pay total before the bank payment is released. That is the control the agent must sit in front of, not replace.
Whether an agent can run payroll end to end is a different question with a short answer. This playbook covers the preparation that takes most of a payroll team's week, inside the bounds described in AI agents for finance.
Which capabilities do you grant, and at what depth?
The payroll system holds some of the most sensitive personal data in the business. Scope the connection tightly, as set out in connecting an AI agent to your payroll system.
- Agent, depth 1: reads approved changes from the HR system. Only records in an approved status, with the approver identity.
- Agent, depth 1: reads payroll records for affected employees only. Not the whole payroll.
- Agent, depth 2: stages changes as pending inputs. Effective date, pro-rating, back pay from the effective date and the reason, linked to the approved record. A payroll specialist approves the batch before it enters the run.
- Agent, held: bank detail changes, one-off payments, retrospective changes beyond a set number of periods and anything without an approved source record.
- Agent, refused: committing inputs, running the calculation for payment, finalising or releasing the pay run.
- Agent, refused: changing pay without an approved HR record. Including when an employee or manager asks by email. See can an AI agent change an employee's salary in payroll.
- Person, payroll specialist: approves the staged batch. A second person approves held items.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Read approved changes | From the HR system | 1 | HR approval |
| Stage inputs | Pending changes with calculations | 2 | Specialist approves batch |
| Bank details | Holds with verification request | held | Verification out of band |
| One-offs, retro | Holds with working | held | Payroll manager |
| Commit and run | Nothing | refused | Payroll team |
| Release net pay | Nothing | refused | Authorised signatories |
How do held items, revocation and the record work?
Held items carry the reason and the evidence a person needs: the approved record, the calculation, the change from last period. A bank detail change shows the old and new details with the date the request arrived and how it arrived. The verification itself, a call to a number already on file or a check through the employee's authenticated self-service, is done by a person.
Revocation is by capability and by population. The payroll manager can withdraw staging for one pay group, such as executives or a country entity, without stopping the rest. Withdrawal takes effect before the next batch. If the agent's certification run clears no depth, it stops staging the same day and the team keys inputs by hand.
Every staged input is filed with the source record, the approver of that record, the calculation and the specialist who approved the batch. When an employee disputes their pay, you can show where every change came from.
Which controls matter, and what evidence does each leave?
Signed source only. A change enters staging only from an approved HR record or a statutory notice. Evidence: source reference and approver on each input.
Batch totals. The agent produces a change report: headcount moves, gross pay change, largest individual changes. Evidence: the report signed by the specialist. Detail on these checks is in checking payroll changes before the payroll run.
Bank detail cooling period. A changed account is not paid until verified and, where policy says so, after a cooling period. Evidence: verification record.
Minimum data. The agent reads only the employees it is changing. Evidence: access log by employee.
Approval matrix. Who approves which payments the agent prepares is written down, as in an approval matrix for agent-prepared payments. Evidence: the matrix version on each approval.
What should you measure?
- Staged inputs rejected or amended by the specialist, by reason.
- Post-payroll corrections caused by input errors, before and after the agent.
- Changes arriving without an approved record. These are upstream process failures.
- Bank detail changes held, verified and refused.
- Time from HR approval to staged input.
Where does it usually go wrong?
Effective dates. A pay rise approved this month but effective two months ago needs back pay. If the agent stages only the new rate, the employee is underpaid. Require an effective date on every change.
Leavers paid after leaving. The leaver record arrives late, after the cut-off. The agent should flag leavers whose last day falls before the period end and who are still in the run.
Duplicate approvals. The same change approved twice in the HR system, once by the manager and once by HR, staged twice. De-duplicate by employee, element and effective date.
Email shortcuts. A director emails payroll to "add a bonus for Sam". It is not an approved record. The agent holds it and names the record that is missing.
Questions people ask
Can the agent stage statutory tax code changes?
Yes, at depth 2, when the notice arrives through the official channel into payroll. A notice forwarded by email is held.
Does the agent see everyone's salary?
It should see only the employees it is changing, and only the fields it needs for the calculation.
What about pay groups in other countries?
Each country's payroll rules differ. Certify the agent separately for each pay group before it stages inputs there.