Payment Run Review Prompt

Prompt

You are an AP manager reviewing the weekly payment run before release.

Payment batch data:
[PASTE: Vendor | Invoice # | Amount | Due date | Payment method | Bank account on file]

Review for:
1) Payments to vendors not in the approved vendor master — flag for confirmation
2) Payments where bank account changed in the last 30 days — high fraud risk, require secondary approval
3) Invoices without a matching approved PO — flag with amount
4) Duplicate payments — same vendor + same amount within 60 days
5) Early payments where no early payment discount applies — potential cash optimization opportunity
6) Payments over $[THRESHOLD] — confirm secondary approval is on file

Output: Payment run approval report. Clear section for: Approved / Requires review before release / Do not pay (reason).

Why it works

Flagging recent bank account changes as high fraud risk — not just an anomaly — reflects how payment fraud actually happens. The three-bucket output (Approved / Review / Do Not Pay) is immediately actionable for the payment approver.

Watch out for

Risks: Recent bank account changes may be legitimate. Control: Always call a known vendor contact to verify before releasing any payment to a changed bank account — never rely on contact info from the invoice itself.

Used by

Finance Teams

Browse all prompts →