No, not on its own. A salary change is a standing instruction that pays out in every future run, so it needs the same protection as a supplier's bank details. An AI agent can prepare the change from a signed pay decision, calculate pro-rata and back pay, and check it against pay bands. A different person enters and approves it.
Why is a salary change riskier than a single payment?
A one-off payment is wrong once. A salary change is wrong every month until someone notices. That makes the payroll master record one of the most attractive targets in a business: a small, quiet increase to a friend's pay, or to a leaver's record that was never closed, can run for a long time inside a total that looks normal.
The risk is the same shape as a change to supplier bank details. The change itself moves no money. It creates a permission for money to move later, repeatedly, without anyone approving each payment again. So the control has to sit at the change, not at the run.
What must be true before the agent prepares a change?
The agent prepares a salary change only when all of these hold:
- the source is a signed pay decision: a pay review outcome, a promotion letter or a contract variation, held in the HR system of record;
- the employee, effective date and new amount in the request match that document exactly;
- the new salary sits inside the band for the role, or the document records an approved exception;
- the request did not arrive only by email or chat from a manager, which is a declared claim, not an approval.
If any condition fails, the agent does not prepare the change. It holds the request and tells the person who sent it what is missing.
Who does what?
| Step | The agent | A person |
|---|---|---|
| Reading the pay decision | Extracts employee, amount, effective date and approver | Signs the decision in the first place |
| Calculating the impact | Works out pro-rata pay, back pay and changes to pension or overtime rates | Confirms any calculation the agent flags as unusual |
| Band check | Compares to the pay band and notes exceptions | Approves an exception |
| Preparing the input | Drafts the change in the payroll input file at depth 2 | Enters or releases it into payroll |
| Pre-run check | Lists every change in the run against its source | Payroll manager signs off the run |
The separation of duties lives in the last two rows. The person who approved the raise, the person who enters it, and the person who approves the run should be three different roles. The agent can be the preparer. It cannot fill any of the other three.
An illustrative example
Take a company of about 300 staff finishing its annual pay review. HR sends a file of 40 changes, each backed by a signed letter.
The agent matches every row in the file to a letter. Thirty-nine match. The fortieth raises a team member's salary from 42,000 to 48,000, but the only support is an email from their line manager asking payroll to "make the increase we discussed". There is no letter, and the new figure sits above the band for the role.
The agent prepares the 39 supported changes as a draft payroll input, with back pay calculated from the effective date in each letter. It holds the fortieth, records why, and sends it to the HR business partner. The payroll officer enters the 39 changes, and the payroll manager approves them in the check of payroll changes before the run. The held change waits until a signed letter exists.
What controls make it safe?
- Read-only access to pay data by default. When you connect an agent to the payroll system, give it read access and a draft input area, not write access to employee records.
- Source over request. The signed document is the authority. An email asking for a change is treated as unverified.
- Bands as a hard bound. A change outside the band is held, however well supported.
- Three roles, three people. Approver of the pay decision, enterer of the change and approver of the run are named and different.
- A filed record per change. The source document, the calculation and each verdict are kept so the change can be reconstructed at audit.
The same principles apply across the rest of payroll, covered in whether an AI agent can run payroll, and across finance generally in AI agents for finance: books you can audit.
Where Pryme fits
In Pryme, preparing a pay change and writing it to the payroll record are separate capabilities. The Pryme Context Protocol marks a signed HR decision as signed and a manager's email as declared, and only the first can support a change. Each verdict, including a hold for a missing letter, is filed with the bound that decided it.
Questions people ask
Can the agent process a salary reduction the same way?
Yes, with the same conditions. Reductions carry extra employment-law risk, so the signed document should show the employee's agreement, and the agent should hold any reduction it cannot match to one.
What about one-off payments such as a bonus or allowance?
These are lower risk than a permanent change but follow the same pattern. The agent prepares them from an approved source and a person enters them.
Can the agent spot changes someone made directly in payroll?
Yes. Comparing each run's pay records with the prior run and with signed decisions is one of its most useful checks. A change with no source document is reported to the payroll manager.