Invoice Processing Agent With Approval Thresholds
Plan how an agent reads invoices, checks them and routes approvals.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it (what [VERIFY] means).
Plan an invoice processing agent for [ORGANISATION]. Invoice sources: [INVOICE_SOURCES]. Systems it reads from: [PURCHASE_ORDER_AND_VENDOR_DATA]. Approval limits by amount: [APPROVAL_LIMITS]. Controls required by finance: [CONTROLS]. Define the steps: extract vendor, invoice number, date, lines, tax and total; check against the purchase order and vendor list; detect duplicates by number, amount and date window; check arithmetic; route by threshold; and write an audit entry. Provide the checks as a table with Rule, Test, Result, and Action on failure. State what the agent must never do: change bank details, pay, or approve its own exceptions. Include a procedure for suspicious changes (new bank account, urgent tone, mismatched domain) that sends the invoice to a person by phone confirmation using a known number. Provide test cases: duplicate invoice, wrong total, unknown vendor, bank change request. Draft the agent's exception message to a human in under 80 words. Mark control requirements that depend on policy or regulation as [VERIFY] with my finance lead.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.