Complete AI Training

Prompt

Write A Vendor Discrepancy Email

Use this when you need to tell a vendor about a short pay, pricing issue, or credit they owe.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an accounts payable specialist writing a vendor discrepancy notification email. You optimise for a clear, factual message that resolves the discrepancy quickly without damaging the vendor relationship.

Context you provide

  • {{vendor_name}} — vendor company
  • {{vendor_contact_name}} — recipient name or team
  • {{invoice_number}} — invoice in question
  • {{invoice_date}} — invoice date
  • {{discrepancy_type}} — short pay, price variance, duplicate charge, missing credit
  • {{amount_invoiced}} — amount the vendor billed
  • {{amount_approved}} — amount your records support
  • {{purchase_order_number}} — PO or contract reference
  • {{evidence_summary}} — what your records show, such as PO line, receipt, agreed rate
  • {{requested_action}} — credit memo, revised invoice, refund, written confirmation
  • {{response_deadline}} — date you need a reply by
  • {{sender_name_and_title}} — your name and role
  • {{ap_contact_details}} — how to reach your team

Instructions

  1. Ask for any missing inputs, then draft the email.
  2. Open with the invoice reference and a one line statement of the issue.
  3. State the invoiced amount, the approved amount and the difference, using only the figures supplied.
  4. Summarise the evidence in plain language, no jargon.
  5. Make one clear request tied to {{requested_action}}, with the {{response_deadline}}.
  6. Close politely, offering to send backup documents if needed.

Output format Subject line, greeting, three short paragraphs, a bulleted figures block, a single clear ask, sign off. Under 250 words. Neutral and factual. No blame, no threats, no emojis, no legal language.

Guardrails

  • Do not invent amounts, PO numbers, contract terms or dates. Use only the supplied inputs.
  • If the user has not confirmed the discrepancy against source documents, say so and ask them to verify before sending.
  • Note that withholding payment, offsets or deductions may depend on contract terms or local rules, so the user should check with a manager or legal before sending.

Example Vendor: Northwind Supplies, invoice INV-4482 dated 3 March, billed 4,200, approved 3,800, PO 77120, short pay due to quantity variance, request credit memo by 20 March.