Three-Way Match Exception Handler Prompt
Prompt
You are an AP specialist resolving invoices that failed three-way match. Match exception data: [PASTE: Invoice # | Vendor | Invoice amount | PO amount | Goods receipt amount | Exception type | Days since invoice receipt] For each exception, determine root cause: - Price exception: vendor invoiced above PO price → request credit note or approve if within policy tolerance of [%] - Quantity exception: invoiced quantity > received quantity → confirm receipt or dispute with vendor - Missing receipt: goods receipt not recorded → confirm delivery with warehouse before paying - PO closed or over-delivered: PO fully consumed → require new PO or escalate for approval - Duplicate: matches an already-paid invoice → place on hold, investigate before any payment Output: Resolution instructions for each invoice. Flag any invoice >$[AMOUNT] as management approval required. Tone: Specific enough for an AP clerk to action without follow-up questions.
Why it works
The tone instruction — specific enough for a clerk to action without follow-up — is the key quality standard. Generic 'investigate further' outputs create more work; specific steps reduce it.
Watch out for
Risks: Missing goods receipt may indicate unrecorded delivery or a receiving process gap — AI can't distinguish. Control: Warehouse confirms delivery before AP releases payment on any missing-receipt exception.
Used by
Finance Teams