Yes, for what they approve, and only for what they could see when they approved it. An AI agent can match invoices and draft a payment run, but it cannot carry accountability. The clerk who releases a held payment owns that release. The business owns the bounds it set and the people it allowed to approve.
Where does accountability sit in an accounts payable process?
Three parties carry it, and a governed record keeps them apart. The agent prepares: it reads the invoice, matches it to the purchase order and goods receipt, and drafts the payment. The clerk decides on anything the agent holds for a person. The business decides who may approve, at what amounts, and which suppliers the agent may pay without review.
Moving money is depth 4 work: it is hard to undo. Most finance teams keep payment release held for a named person, so the clerk's approval is the moment the decision becomes theirs. Matching and drafting at depth 2 are the agent's work, and a matching error the clerk could not reasonably have spotted is a process failure, not a personal one.
What may the agent do, and what stays with the clerk?
| Task | The agent | The clerk |
|---|---|---|
| Read invoices and statements | Depth 1, alone | Spot checks |
| Three-way match and coding | Depth 2, drafts the match | Confirms exceptions |
| Payment within routine bounds | Held for a named person | Approves or rejects |
| New or changed supplier bank details | Refused as a payment source | Verifies by call-back to a known number |
| Duplicate invoice suspected | Holds and flags | Decides |
The bank-details row matters most. An emailed invoice is an external source. Under a governed setup, an external claim cannot authorise a payment, so the agent will not pay to new details on the strength of an email. If the clerk then changes the supplier record by hand without verifying it, the decision and the accountability are theirs.
What does the record show about who decided?
Every verdict the agent reaches is filed in an append-only record. For a held payment, it shows the invoice, the matched documents and the provenance of each: whether the supplier's bank details came from a sealed vendor master or arrived in an email. It names the bound that held the action, the clerk who approved it, the time, and what the clerk saw on screen.
That record protects a careful clerk as much as it exposes a careless one. If the agent presented an external bank change as if it were verified, the record shows the failure sat in the agent's sources or bounds, and responsibility moves to whoever designed them. If the warning was on screen and the clerk approved anyway, the record shows that too.
An example: the 4,000 invoice with new bank details
Take a mid-sized distributor. A supplier invoice for 4,000 arrives by email with a note that the supplier has changed banks. The agent matches it to a valid purchase order, flags the new details as external, and holds the payment. The clerk is clearing a backlog before a payment run, sees a valid match, updates the vendor record and approves.
The money goes to a fraudster. The record shows the external flag, the hold, the reason, and the clerk's approval two minutes later with no call-back logged. The clerk is accountable for that approval. The finance manager is accountable for letting someone approve bank-detail changes without having shown, in practice, that they treat external claims as unverified.
Which controls keep accountability fair?
- Approval rights follow competence. Only clerks who have shown they can read provenance and recognise a held payment's reason may release payments. A practice some businesses adopt is to tie approval rights to a current certificate.
- Practice on real cases first. A two-week practicum for accounts payable clerks gives new reviewers supervised decisions before they approve alone, and a practicum log template keeps the evidence.
- Keep reviewers current. Agent certificates lapse after 90 days and bounds change, so plan for preparing clerks for each 90-day recertification.
- Separate bank-detail changes from payment release. The person who verifies new details should not be the one approving the first payment to them.
The same logic applies in other roles; compare how it works for paralegals who approve what an agent drafts. For the wider picture of literacy and credentials, see AI literacy and certification for people who work with agents.
Where the Academy fits
Pryme Intelligence Academy's Operator track covers human review, held actions and reading the workspace, with module tests set in the learner's own industry and role. The Certified Pryme Operator practicum is two weeks of real review decisions, signed off by a Pryme assessor, with no missed red line allowed. For an accounts payable team, paying on an unverified bank change is exactly that kind of red line.
Questions people ask
Can a clerk be blamed if the agent matched the wrong purchase order?
Only if the mismatch was visible and the clerk approved without looking. If the agent presented a clean match built on a wrong source, the record shows the fault was in the match, and the fix belongs to whoever owns the agent's sources and bounds.
Does approving in bulk change accountability?
No. Approving fifty held payments in one click is fifty approvals. Many teams switch off bulk release for held payments for exactly this reason.
Who is accountable when the agent pays without a person?
If a payment ran within bounds the business set, the people who set those bounds own the outcome. The record names the bound that allowed it, so the question is answerable.