Guide · finance controls

Approving AI agent payments: a guide for finance controllers

What you want as a controller is what you already have for people: payments over a limit are decided by the person who owns that limit, nobody approves their own request, and every payment has a record an auditor can test. An agent that matches invoices and proposes payments changes who raises the payment, not the controls you answer for. The work is making those controls apply to the agent, at the point where the money moves.

The controls an agent payment needs

ControlWhy it matters
A limit per payment and a running totalTwo payments of 9,000 to one supplier in an hour are one payment of 18,000. A limit that looks at each request alone is a limit an agent can walk under without meaning to.
The right approver by amount and supplierThe decision belongs to whoever holds that authority, not whoever set the agent running.
What the approver seesThe invoice, the supplier, the amount and what is unusual about it, on the screen where they answer, not in a system they would have to open.
Correct, not just rejectMost bad proposals are one wrong figure. The approver fixes it and the corrected figure is the one that is paid.
Segregation of dutiesAn agent never approves anything, and the person who raised a request is not one of its approvers.
The payment checks the yesThe system that pays should refuse a payment nobody agreed to, rather than trust the agent to have asked.
One yes, one paymentAn approval is spent when it is used. A retried run must not pay twice.
Evidence per paymentWho was asked, what they saw, what they decided, when, and what was paid, exportable for the auditor.

An approval the payment never checks is a record of intentions

The common failure is an approval step that sits beside the payment rather than in front of it: the agent asks, a person says yes, and the payment run never looks at the answer. It reads well in a control description. It does nothing the day the agent skips the question, retries with a different figure, or pays a supplier nobody saw.

The fix is to make the approval something the paying system can check. The yes travels with the payment as a signed token bound to the supplier and the amount that were agreed, and the payment service refuses any request without a valid one. Asking then stops being a convention the agent follows and becomes the only way a payment goes out.

Building it yourself

  • Your ERP's approval matrix may be enough when the agent only drafts payments and a person still raises them in the ERP.
  • Build it when one agent pays from one system and you can add the check to that system's code.
  • Buy it when several agents or systems pay, when approvers work in Teams, email or on their phones, or when the auditor will want one record across all of them.

How Deliverd does it

The agent declares the payment at a gate before it pays, with the supplier, amount and invoice, and gets one of three answers: allowed, refused, or a named person decides. Rules with conditions on the amount and the supplier, included in Business Starter, Business and Enterprise, settle the routine cases, and a rule can add up earlier requests in a window, grouped by supplier, so split payments are judged as one. The approver answers from Teams, Slack, email or a page built for a phone, sees what was noticed as unusual, and can correct a figure before agreeing.

A payment that may go ahead carries a signed decision token bound to the action, a hash of the agreed input and a short expiry. Your payment service checks it with the SDK or one HTTP call and turns away a payment of 1,240 against a yes for 1,200. Recording the payment spends the yes, and a second use is refused. Deliverd does not see the payment itself: the token check in your payment code is what ties the two together. Every step exports as a signed evidence pack in JSON, CSV or PDF.

Questions

Does this replace the approval matrix in our ERP?
No. Keep it for payments people raise. Deliverd covers the payments an agent proposes, with the same idea: the person who holds the limit decides, and the record is kept.
How are split payments caught?
A Deliverd rule can add up earlier requests over a window, grouped by supplier and by agent, so two payments of 9,000 within an hour count as 18,000 against a 10,000 limit.
Can the agent approve its own payment?
No. In Deliverd an agent may not approve anything, and the person who made a request is removed from its approvers.
What if the agent pays without asking?
Then it has no decision token. When your payment service checks for one, a payment without a valid token for that supplier and amount is refused there.