Can an AI agent pay supplier invoices?

It can prepare the payment; it should not release it. An AI agent can select approved invoices that are due, check each one for duplicates and recent bank detail changes, and build the payment file. Releasing that file at the bank moves money, which is depth 4. Two authorised people release it, and neither approved the underlying invoices.

Where does payment sit in purchase-to-pay?

Payment is the last step of purchase-to-pay, after the order, the receipt, the invoice and its approval. By the time an invoice reaches the payment run, several people have already looked at it. That creates a temptation to treat payment as a formality and let the agent finish the job.

Resist it. Payment is the step where every earlier failure becomes a loss: the duplicate nobody spotted, the bank details changed last week by a fraudster, the invoice approved by someone who should not have approved it. Once the money leaves, getting it back depends on the other party's cooperation. The release is the last control that can stop it.

What does the agent prepare?

Selection: - invoices approved and due by the run date, under payment terms; - early-payment candidates where a discount applies and policy allows; - invoices on hold excluded, with the reason listed.

Checks on each line: - a duplicate check against paid and pending invoices, as set out in how to detect duplicate supplier invoices; - bank details unchanged since the last payment, or changed and verified through the call-back process; - supplier not newly created within the cooling-off period; - amount within the approver's authority on the invoice; - payee name check result, where the bank offers one.

Output: - the draft payment file; - a summary for the releasers: total, number of payments, largest payments, first payments to new suppliers and any line with a warning.

All of this is depth 2. The agent assembles and checks. It does not log in to the bank and press send.

Which step keeps the separation of duties?

Release, by two people who did not approve the invoices. Invoice approval says "we owe this". Release says "we are paying this, now, to this account". If one person can do both, they can approve and pay a false invoice alone. The agent prepares for both decisions and holds neither.

Approvers of large or unusual runs should read the agent's summary, not just the total. The useful lines are the exceptions: a first payment to a new supplier, a changed bank account, a payment far above that supplier's usual amount.

An illustrative example

Take an engineering firm that runs supplier payments twice a week. On Tuesday the agent selects 180 approved invoices due by Friday, totalling 1.1 million.

Its checks hold four. Two are the same invoice from a subcontractor, entered once from email and once from post. One is to a supplier whose bank details changed six days ago; the change was verified, but policy requires a ten-day cooling-off period, so the agent moves it to the next run. The fourth is a payment of 96,000 to a supplier the firm usually pays about 5,000 a month. The invoice was approved by a project manager whose limit is 100,000. Nothing is wrong on paper, but the agent flags it.

The AP lead checks the fourth and finds it is a genuine annual equipment purchase. The finance manager and financial controller release the run of 177 payments at the bank.

What controls make it safe?

• No bank release rights for the agent. Enforced in the bank's own user set-up.
• Two releasers, named, outside invoice approval.
• Exception summary on every run. Releasers see what changed, not just the total.
• Cooling-off periods for new and changed bank details.
• The payment file is locked after review. Any edit after the summary is produced restarts the review.
• Everything filed. Selection, checks, summary and release are linked.

Where Pryme fits

In Pryme, building a payment file and releasing one are separate capabilities. Payment release is held for named people, and the verdict on every line, including those moved to a later run, is filed with the bound that decided it.

Upstream, the work of processing supplier invoices determines how clean the payment run is; the full flow is in how to process supplier invoices from inbox to ledger. The wider controls are in AI agents for finance: books you can audit.