No. An AI agent can prepare a payment run, check every line against invoices, approvals and supplier records, and flag anything unusual, but the approval that releases the money should belong to a named person. A payment run moves money out of the business in bulk, often irreversibly, and approving it is the control that everything before it depends on.
Why is approval the line?
A payment run is the point where errors and fraud turn into losses. Up to that moment, a wrong invoice, a changed bank detail or a duplicate is a record that can be corrected. After release, it is money in someone else's account. That is why finance teams separate preparing a run from approving it, and why approval sits with people who are accountable for it.
On the depth scale, releasing payments is depth 4: moving money or taking actions that are hard to undo. An agent might in principle earn some depth 4 capabilities with enough evidence, but approving a whole run is different. It is the independent check on the preparer. If the agent is also the preparer, it would be checking itself; if another agent approves, the check is no longer independent of the system that built the run. The case is made in full in the payment approver must never be the agent.
What conditions would have to change for that answer to change?
None that most businesses should accept. You could imagine a tightly bounded case, such as recurring payments of fixed amounts to long-standing payees, released automatically under a standing approval a person gave in advance. But that is a person approving a schedule, not an agent approving a run. The standing approval should be specific, limited and reviewed.
What may the agent do, and where does the named approver sign off?
| Step | The agent | Named approver |
|---|---|---|
| Select invoices due | Builds the run from approved, due invoices | Nothing |
| Three-way match | Confirms purchase order, receipt and invoice agree | Reviews exceptions |
| Duplicate check | Flags possible duplicates across the run and history | Decides |
| Bank detail check | Flags payees whose details changed within a set period and whether verification is recorded | Confirms verification before approving |
| New payee check | Flags first-time payees | Reviews them individually |
| Totals and cash | Shows the total against available cash and forecast | Decides whether to pay in full or defer |
| Approval and release | Prepares the approval pack | Approves and releases |
The agent's value is in making the approver's review fast and focused. Instead of scanning hundreds of lines, the approver sees a short exceptions list with evidence. The checks belong on a standard payment run review checklist.
An illustrative example
Take a regional housing association running a weekly supplier payment run of around 200 invoices.
The agent builds the run and checks it. It finds 196 clean lines. It flags four: one supplier's bank details changed nine days ago, with a call-back verification recorded; one invoice that matches an amount and date paid last month to the same supplier; one first-time payee; and one invoice approved by someone whose limit is lower than the invoice amount.
The finance manager reviews the four. The bank change is verified; she accepts it. The possible duplicate is a genuine duplicate; she removes it. The new payee is a contractor set up properly; she accepts it. The over-limit approval goes back to the budget holder's manager. She approves the run of 198 lines and releases it. The agent's work cut her review from an afternoon to a short session; her approval kept the control.
Which controls hold the line?
- No release permission. The agent's credentials in the payment system cannot approve or release. The restriction sits in the system, not in the agent's instructions.
- Two people for large runs. Above a threshold, a second named approver signs.
- Exceptions listed, not buried. The approval pack leads with flags and evidence.
- Approvals recorded with who approved, what they saw and when.
Whether the same agent can prepare and approve an individual payment raises the same issue at smaller scale; see whether the same AI agent can prepare and approve a payment. Invoice approval within limits is a different, lower-risk step earlier in the process, described in letting an AI agent approve invoices in your AP tool within limits, and the purchase stage before that in whether an AI agent can approve purchase orders.
Where Pryme fits
In Pryme, preparing a payment run and approving it are separate capabilities, and approval is held for a named person on every finance agent. Bank details from emails arrive as external, and an external claim cannot authorise a payment. Every verdict is filed. More is in AI agents for finance: books you can audit.
Questions people ask
Can the agent release a run after a person approves it?
It can carry out the release a person approved, exactly as approved, if your controls allow it. It must not change the run between approval and release.
What if the approver is away and payments are due?
Use a named deputy with the same authority. The agent does not step in.
Should the agent ever remove lines from a run?
It can propose removing lines with reasons. The approver decides.