Within narrow limits. An AI agent can approve low-value purchase orders for catalogue items from approved suppliers, where the budget line has room and the amount is under its limit, if it did not raise the order itself. New suppliers, orders over budget or limit, capital spend and anything that commits the business to a contract need a named approver.
What makes a purchase order safer to approve than a payment?
A purchase order commits the business to buy, but no money moves yet. Goods must still be received, the invoice matched and the payment approved. Each later step is a check on the earlier one. That gives purchase order approval more room for automation than payment approval, which is the last control before money leaves. The difference is clear when you set it beside whether an AI agent can approve a payment run.
But "no money yet" is not "no risk". A purchase order can create a binding commitment with the supplier, use up a budget, and start the chain that ends in payment. The approval is where spending is authorised, and that authority belongs within a delegation of authority with named people at the top of it. Background on the document and the process is in what a purchase order is and what purchase-to-pay is.
Which conditions decide it?
The agent may approve only when every condition holds:
- Approved supplier already set up and verified in the supplier master.
- Catalogue or contracted item, at the agreed price.
- Budget available on the cost centre and line, read from the budget system at the time.
- Under the agent's limit, per order and per requester per month, set by finance.
- Separation: the agent did not create the order, and the requester is not the budget holder approving their own spend through the agent.
- No splitting: the order is not one of several to the same supplier that together exceed the limit.
If any condition fails, the order is held for the named approver in the delegation of authority.
What may the agent do, and where does a named approver sign off?
| Purchase order | The agent | Named approver |
|---|---|---|
| Stationery from the contracted supplier, within budget, under limit | Approves at depth 3 | Samples monthly |
| Same, but budget line nearly exhausted | Holds with budget position | Budget holder |
| New supplier | Holds; new suppliers need onboarding and checks first | Procurement and budget holder |
| Above the agent's limit | Checks it and prepares the approval with evidence | Approver per delegation of authority |
| Capital expenditure | Prepares | Capex approver |
| Services under a new contract | Prepares | Legal and budget holder |
| Several small orders that together exceed the limit | Flags the pattern | Procurement |
The splitting row matters. Breaking one purchase into several small ones to stay under approval limits is a known way around controls, by people and potentially by an agent optimising for speed. Counting by requester, supplier and period catches it.
An illustrative example
Take a university facilities team. The agent has a limit of 500 per order for catalogue items from contracted suppliers.
A technician raises a purchase order for cleaning supplies worth 320 from the contracted supplier. The cost centre has budget, the items are in the catalogue at contract prices, and the agent did not raise the order. The agent approves it and it goes to the supplier.
The same technician raises three orders for laboratory consumables from the same supplier on the same day, each worth 450. Each is under the limit. Together they are 1,350. The agent holds all three and flags the pattern to the budget holder, with the three orders side by side. The budget holder confirms they are for three different labs, approves them, and asks procurement to raise the agent's limit for that category with a monthly cap. The pattern check did its job.
Which controls make it safe?
- Limits and budget checks in the purchasing system, not only in the agent's instructions.
- No self-approval: if the agent raised the order, as described in letting an AI agent create purchase orders in your ERP, a person approves it.
- Supplier master read-only for the approving agent.
- Approvals filed with the conditions checked and their sources.
- Matching downstream: invoices are matched to the order and receipt before payment, as covered in whether an AI agent can match invoices to purchase orders.
Where Pryme fits
In Pryme, purchase order approval is certified per category on your own past orders, with your delegation of authority as the customer's own limits in the minimum chain. Raising an order and approving it are separate capabilities that one agent never holds together. More is in AI agents for finance: books you can audit.
Questions people ask
Can the agent approve orders against a framework contract?
If the contract's prices and limits are loaded as an approved source and the order fits them, yes, within the agent's own limit.
Who sets the agent's approval limit?
Finance, within the delegation of authority, with sign-off from whoever owns that delegation. It should be written down and versioned.
Should requesters know an agent approved their order?
Yes. It helps them understand why some orders go through quickly and others wait for a person.