Guide

Controls a CFO should demand before letting agents pay

30 October 2026

finance · cfo · aiagents · controls

This article was created with the help of AI by the Screwtape.ai team. Product details were checked against screwtape.ai/pricing, /docs and /openapi.json on 2026-10-24.

AI agents are moving from reading invoices to proposing and releasing payments. Before you let one near the payment run, ask for the same controls you would expect of a new AP clerk, plus a few that only matter for software.

The checklist

1. A check that isn't the agent. The agent that decided to pay should not be the one confirming it was right. Ask for a separate step, run outside the agent, before money moves.

2. Duplicate detection before payment. Vendor, invoice number and amount compared against what has already been processed, with a rule for near-duplicates (same vendor, same amount, close dates). "Possible duplicate" should stop the payment and go to a person.

3. Basic invoice checks. Required fields present. Line items plus tax equal the total. Amount, vendor and terms match the purchase order.

4. Policy rules written down, not prompted. Amount caps, an approved-vendor list, and a second approval above a threshold. These should be rules the system enforces, not instructions in a prompt the agent may ignore.

5. Single-use, short-lived approvals. An approval should be bound to one invoice, one amount and one vendor, and expire in minutes. An approval the agent can reuse is a blank cheque.

6. A record you can verify. Every decision signed and kept, linked so gaps or edits show, and exportable for your auditor.

7. A hard stop. A spending or call limit that stops by default, rather than silently continuing.

8. A person in charge. Escalations go to a named human. Automated checks reduce risk; they don't remove it.

Where Screwtape.ai fits

Screwtape.ai decides whether an AI agent is allowed to spend money, and keeps the proof. It is a separate check that runs outside your agent, covering items 1–7 above:

• duplicate invoice check and invoice checks (required fields, totals, purchase order match),
• policy rules: amount caps, vendor allowlist, second approval, required fields (Team and Finance Control plans),
• 15-minute single-use pass tokens bound to the exact invoice, amount and vendor (both plans),
• signed, linked, tamper-evident receipts with export; 1-year retention on Team, 7-year retention and an auditor export bundle on Finance Control,
• hard stop at the plan limit by default; overage is opt-in and capped.

Verdicts are produced by AI models and automated checks and can be wrong. Item 8 is yours.

See the plans for finance teams: screwtape.ai/pricing.