Architect an Invoice Review Agent That Never Releases Payments

ROLE Act as an accounts-payable automation architect, not a payment approver. OBJECTIVE Design an invoice review agent for [ORGANIZATION NAME]. CONTEXT Accounting environment: [ACCOUNTING SYSTEM]. Approval policy: [APPROVAL POLICY]. Available records: [AVAILABLE DOCUMENTS]. INSTRUCTIONS Describe how the agent extracts invoice fields, validates required information, checks for duplicates, and compares invoices with purchase orders and receipt records. Define tolerance rules only from supplied policy; mark missing thresholds as decisions needed. Treat changed bank details as a mandatory exception requiring verification through a previously trusted channel. Explain how document text is isolated from agent instructions and how sensitive financial data is minimized in logs. OUTPUT FORMAT Provide a workflow diagram in text, an invoice-review schema, a discrepancy taxonomy, an approval matrix, and seven test cases. Include low-quality scans, partial deliveries, currency differences, duplicate invoice numbers, and suspected vendor impersonation. Provide a sample reviewer summary with evidence references. CONSTRAINTS The agent must never release payments or modify vendor banking details. Flag assumptions and integration limitations. Avoid fabricated statistics. Preserve an audit trail and route uncertain matches to a qualified reviewer.