Payroll administrators approve the agent's one-off pay adjustments and query replies. Employee bank detail changes are held and verified through a channel on file by someone other than the person who received the request. The pay run needs the payroll manager plus a finance approver. Nobody approves anything on their own pay record, and rights lapse with certificates.
What does the payroll approver rule cover, and who owns it?
Payroll teams calculate and pay people correctly and on time, every period, with no tolerance for error from the people being paid. Agents help by reconciling inputs from HR and time systems, answering pay queries, preparing adjustments and building the pay run for approval. The approver rule names who releases each held action. It sits alongside your existing payroll controls; it does not replace them.
The payroll manager owns the rule. The financial controller signs it off. The agent owner configures it. Our explainer on what a house rule is covers the rules that let the agent act alone on routine items, and our guide to AI agent skills by role covers what payroll administrators need to know.
What are the steps?
- Payroll manager: lists the agent's actions by depth. Depth 1: reads HR changes, timesheets, prior payslips and tax settings. Depth 2: drafts replies to pay queries and adjustment proposals. Depth 3: applies routine inputs within house rules, such as approved overtime from the time system. Depth 4: applies one-off adjustments, changes bank details, releases the pay run.
- Payroll manager: assigns one-off adjustments to a payroll administrator, with the payroll manager above a set amount.
- Payroll manager: holds every bank detail change for verification through a channel already on file, released by an administrator who did not receive the request.
- Payroll manager: assigns the pay run to themselves plus a finance approver, with a variance report against the last period.
- Payroll manager: bars self-approval on any item affecting the approver's own pay.
- Payroll manager: ties each role to a current certificate. Agent owner configures and files.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Reconcile inputs | Matches HR and time data | 1 | Nothing |
| Routine input | Applies within house rules | 3 | Nothing |
| Pay query | Drafts reply | 2 | Administrator sends where held |
| One-off adjustment | Prepares and holds | 4 | Administrator; manager above set amount |
| Bank detail change | Holds for verification | 4 | Administrator who did not receive it |
| Pay run | Builds with variance report | 4 | Payroll manager plus finance |
Why is a bank detail change treated like a payment?
Payroll diversion fraud is simple: someone emails payroll pretending to be an employee and asks for their salary to go to a new account. The next pay run sends it there. By the time the real employee notices, the money has gone. A change of bank details is a payment instruction in disguise.
So the rule holds it. The request's provenance is shown to the approver: an email is external, a change made in the employee self-service portal after login is signed. The administrator who releases the change confirms it through a channel already on file, not one in the request. They are not the person who received the request, because that person may have already been persuaded.
The pay run is the other high-impact approval. The agent's variance report should show headcount change, total pay change, new bank accounts since last period, and the largest individual changes. Approvers start there.
Which controls make the rule work, and what evidence do they leave?
Verified bank changes. Evidence: verification channel and approver name on each change, as set out in the approver authority matrix for the payroll team.
Two approvers on the pay run. Evidence: payroll manager and finance names, and the variance report they saw.
No self-approval. Evidence: approver names compared with the employees affected.
House rules for routine inputs. Evidence: each routine input matched to a house rule.
Rights lapse with certificates. Evidence: certificate status on each approval date.
What should you measure?
- Pay errors reported by employees, by cause.
- Bank changes without recorded verification. The target is none.
- New bank accounts in the pay run, checked every period.
- Pay runs released with one approver. The target is none.
- Administrator coverage over pay day, using the competency matrix for the payroll team.
Where does it usually go wrong?
Pay day pressure. The run is late, the finance approver is away, and the payroll manager releases alone. Name a deputy approver in finance.
Variance reports are not read. Approvers glance at the total. Ask them to note one item from the report on each approval, so the record shows the report was read.
Agent replies give tax advice. A pay query about tax codes gets a confident answer. Scope the agent to explain the payslip and route tax questions.
Rules are borrowed from lending or onboarding. Compare the approver rule for the lending team and the approver rule for the onboarding team: helpful on verification, but payroll's fixed pay date creates its own pressure.
Where the Academy fits
Pryme Intelligence Academy's Operator track trains payroll administrators and managers in human review, usage and billing, and when something goes wrong, with module tests set in their own industry and role. A business can make pay run approval depend on a current Certified Pryme Operator certificate, valid 12 months and renewed with an update module and a short quiz.
Questions people ask
Can the agent run payroll without approval if nothing changed?
Even an unchanged run moves money to every employee. Most firms keep the pay run held for approval every period, with the variance report making a quiet month a quick approval.
Who approves the payroll manager's own pay changes?
The finance approver or another senior person outside payroll. The rule should name them.
Should employees be able to change bank details themselves?
Self-service after strong login is usually safer than email requests. The agent can still hold changes made shortly before a pay run for a quick check.