The failure mode procurement and treasury recognize
Invoice matching is tedious. Teams want agents to do it. The failure is treating a clean match as permission to disburse. Payment release is money plus an external counterparty. Category rules that shipped in real procurement automation are blunt: anything that touches money or an outside party is draft-only until a human approves — no exceptions, not “under the limit.”
A single-agent path to payment is the opposite of maker-checker. Threshold-only invoice approval (the AP agent signs off below $10k) does not cover the wire. Dual approval is two named humans before execution, or one human plus a hard block if the second chair is empty — not the agent approving its own draft.
What LoopLabs demonstrates
In the live control plane, money movement and external-party actions are gated categories outside the prompt. The demo's refund rule (charges or refunds over $500 need a human) is the same shape as supplier payment: the model cannot self-authorize a disbursement. We do not fake a bank rail on the demo screen — we show the approval queue and receipt the payment action must hit first.
Category gate, not a vibe check
Supplier payment is money + external party. Policy says always queue. The agent cannot argue that the match was clean enough to skip.
Dual humans, not agent + agent
Above your materiality line, two independent approvers. The drafter (human or agent) is not the only signer. That is SoD, not a second prompt.
Approval ≠ paid
Log the approve decision, then log the ERP or bank result separately. If the wire fails after approval, the trail still shows both facts.
New vendor / new bank details
IBAN or account changes route to a human at any amount. Duplicate-invoice and unapproved-vendor checks sit in the same gate.
The first policy to ship
- Supplier payment release never auto-executes — agent drafts, humans approve, then the ERP or bank runs.
- Above materiality, require two independent approvers (maker-checker). The agent does not count as a checker.
- New vendor, changed bank details, or split payments against one invoice always escalate.
- Every approval and every payment result write separate receipts: vendor, amount, policy version, approver ids, timestamp.
- Weekly review: repeated single-path payment attempts mean the integration credential is too wide, not that the agent is 'wrong.'
Related guides
Invoice matching without payment release is AP threshold approval. Customer-money the other direction is support refunds above limit. Wrong recipient on the vendor file is contract amendment to the wrong contact.