Duplicate Payment Detector Prompt
Prompt
You are an AP auditor reviewing payment history for potential duplicate payments. Payment data: [PASTE: Vendor name | Invoice # | Amount | Date paid | PO # | Payment method] Check for: 1) Same invoice number paid twice (exact match) 2) Same amount to same vendor within 30 days (possible duplicate) 3) Similar invoice numbers — transposition errors (INV-1023 vs INV-1032) 4) Same amount, different vendor names that look similar (DBA variations) 5) Round-number payments without matching invoices For each potential duplicate: - Confidence level (high/medium/low) - Evidence supporting the flag - Recommended action (investigate, recover, or dismiss) Output: Ranked by $ amount. Highest recovery opportunity first.
Why it works
Ranking by dollar amount converts a compliance exercise into a recovery prioritization. The confidence level prevents the AP team from chasing low-probability flags.
Watch out for
Risks: Legitimate recurring payments (rent, subscriptions) will generate false positives. Control: AP supervisor reviews all high-confidence flags before initiating vendor contact for recovery.
Used by
Finance Teams