How to Write ChatGPT Prompts for AP Exception Handling

Key Takeaway: Most AP exception handling is the same 10 situations, handled manually, over and over again. ChatGPT can investigate, draft responses, and suggest resolutions for the majority of them, if you know how to prompt it correctly. This guide gives you the exact prompts, ready to use.

TL;DR

AP teams burn most of their day on the same 8 exception types: price discrepancies, duplicate invoices, missing GRNs, contract overcharges, no-PO invoices, payment status inquiries, partial deliveries, and exception documentation. ChatGPT can investigate each of these, draft the vendor communication, and produce audit-ready documentation in under a minute, if the prompts are structured correctly. This guide gives you the exact prompts to copy, a base structure that works for any exception type, and a four-step system for turning individual prompts into a repeatable team workflow.

Every AP team has a version of the same Tuesday morning. The inbox has 23 unread vendor emails. Six invoices are sitting in exception queues. Three approvals are stalled waiting for someone to investigate a discrepancy. And the team is already behind before 9am.

The frustrating part is that most of these exceptions are not genuinely complex. They are the same patterns, repeating endlessly: a price that doesn't match the PO, a missing goods receipt, an invoice submitted twice, a vendor asking where their payment is. The work isn't intellectually demanding. It's just endless.

ChatGPT can handle a significant portion of this work, not as an autonomous system running in the background, but as a tool you actively use to investigate faster, draft responses more quickly, and resolve exceptions with better documentation. The key is knowing how to prompt it.

This guide gives you 8 prompt categories with exact templates for the most common AP exception types. Every prompt is ready to copy.

What ChatGPT Can and Can't Do for AP Exceptions

Before we get into the prompts, let's be clear about what we're working with.

What ChatGPT can do well:

• Analyse the information you paste into it and identify the likely cause of an exception
• Draft professional vendor communication in seconds
• Suggest resolution paths based on the situation you describe
• Create consistent documentation for your audit trail
• Help you write better policy-aligned responses than you'd write under time pressure
• Work through complex multi-party situations and lay out the options clearly

What ChatGPT cannot do:

• Access your ERP or live invoice data directly
• Pull vendor history or contract terms unless you paste them in
• Take any action, it can only analyse and advise
• Replace human judgment on genuinely ambiguous financial decisions

With that established, here are the prompts.

How to Structure Every AP Exception Prompt

Before the specific templates, a structure that works for every exception type:

You are an experienced accounts payable
specialist. I'm going to give you the
details of an invoice exception.

Please:
1. Identify the likely cause of the exception
2. Recommend the most appropriate
   resolution path
3. Draft any vendor communication needed
4. Suggest what documentation I should
   retain for the audit trail

Here are the details:
[paste exception details here]

This base structure works for almost anything. The specific templates below are refined versions of this for each exception type.

Prompt 1. Price Discrepancy Exception

The situation: Invoice price doesn't match the PO price or contracted rate.

This is the most common exception type in most AP operations. The cause is usually one of five things: a vendor billing at list price instead of contracted rate, a price increase that wasn't formally agreed, a unit vs. total price confusion, a quantity difference driving the total, or a genuine billing error.

You are an experienced AP specialist
investigating a price discrepancy exception.

Here are the details:
- Vendor name: [vendor name]
- Invoice number: [invoice number]
- Invoice date: [date]
- Invoice amount: [amount]
- PO number: [PO number]
- PO amount: [amount]
- Contracted rate (if known): [rate]
- Difference: [amount and percentage]
- Any relevant context: [e.g. recent rate
  change discussion, contract renewal date]

Please:
1. Identify the most likely cause of
   this discrepancy based on the details
2. Recommend whether to: approve as-is,
   request a credit note, hold pending
   clarification, or escalate to procurement
3. Draft a professional email to the vendor
   requesting clarification or a credit note
   as appropriate
4. Suggest what to document in the
   exception log for audit purposes

Keep the vendor email professional,
specific about the discrepancy, and
request a response within 5 business days.

What you get back: A diagnosis of the likely cause, a clear recommendation on how to resolve it, a ready-to-send vendor email, and audit documentation language, all in under 30 seconds.

Prompt 2. Duplicate Invoice Exception

The situation: The same invoice (or a very similar one) has been submitted twice.

Duplicate invoices are one of the most expensive exception types, and one of the easiest to accidentally pay if the second submission arrives with a slightly different invoice number or date.

You are an experienced AP specialist
investigating a potential duplicate
invoice submission.

Here are the details of the two invoices:

Invoice 1:
- Vendor: [vendor name]
- Invoice number: [number]
- Invoice date: [date]
- Amount: [amount]
- Payment status: [paid / pending / approved]

Invoice 2:
- Vendor: [vendor name]
- Invoice number: [number]
- Invoice date: [date]
- Amount: [amount]
- Payment status: [pending]

Additional context: [e.g. vendor recently
changed billing system, different contacts
submitted each invoice]

Please:
1. Assess whether this is likely a true
   duplicate, a resubmission, or a
   legitimate second invoice
2. Recommend the appropriate action
3. Draft a vendor communication if
   clarification is needed
4. Suggest how to document this
   in the exception log

If this is a true duplicate, draft
the communication to firmly but
professionally decline the second
payment and request confirmation
the duplicate has been cancelled.

Prompt 3. Missing Goods Receipt / Three-Way Match Failure

The situation: The invoice can't be matched because no goods receipt (GRN) has been recorded against the PO.

This is a procurement and AP coordination problem. The goods may have been received without a GRN being raised, or the GRN may be in progress, or the goods may genuinely not have arrived yet. A three-way match failure like this is one of the most common reasons invoices sit in exception queues for days.

You are an AP specialist investigating
a three-way match failure. The invoice
cannot be matched because no goods
receipt has been recorded.

Details:
- Vendor: [vendor name]
- Invoice number: [number]
- Invoice date: [date]
- Invoice amount: [amount]
- PO number: [PO number]
- PO date: [date]
- Expected delivery date: [date if known]
- Requesting department: [department]
- Current GRN status: [not raised /
  partial / unknown]

Please:
1. Identify the most likely reason
   for the missing GRN
2. Recommend the resolution steps
   and who needs to be contacted
3. Draft an internal message to the
   requesting department asking them
   to confirm receipt and raise the GRN
4. Draft a holding message to the vendor
   if payment will be delayed past
   the due date
5. Suggest audit documentation language

Keep both communications professional.
The internal one should be direct and
specific about what action is needed
and by when.

Prompt 4. Vendor Overcharge / Billing Above Contract

The situation: The vendor has billed at a rate higher than the contracted rate, either incrementally or significantly.

This is different from a simple price discrepancy. This is a contract compliance issue. The framing of the communication matters here.

You are an AP specialist and contract
compliance reviewer. A vendor has
submitted an invoice that exceeds
the contractually agreed rate.

Details:
- Vendor: [vendor name]
- Contract reference: [contract number
  or description]
- Contracted rate: [rate]
- Invoiced rate: [rate]
- Difference per unit: [amount]
- Total invoice amount: [amount]
- Amount billed above contract: [amount]
- Contract expiry date: [date]
- Has this happened before: [yes/no,
  and if yes, how many times]

Please:
1. Assess whether this is likely
   an administrative error or a
   deliberate billing practice
2. Draft a formal vendor communication
   citing the specific contract terms
   being violated and requesting a
   corrected invoice or credit note
3. Recommend escalation steps if
   the vendor disputes the contracted rate
4. Suggest what to document and
   whether procurement should be notified

The vendor communication should be
formal in tone, reference the
specific contract clause if provided,
and give the vendor a clear deadline
to respond with a corrected invoice.

Prompt 5. Invoice Without a PO

The situation: An invoice has been received for spend that was never formally approved through a purchase order. Classic maverick spend.

You are an AP specialist handling
an invoice received without a
corresponding purchase order.

Details:
- Vendor: [vendor name]
- Invoice number: [number]
- Invoice date: [date]
- Invoice amount: [amount]
- Service/product description: [description]
- Department that appears to have
  engaged the vendor: [department]
- Any email or communication
  confirming the engagement: [paste
  relevant snippet or note "none found"]
- Is this vendor on our approved
  vendor list: [yes/no/unknown]

Please:
1. Assess whether this invoice should
   be approved retroactively, held
   pending approval, or rejected
2. Identify what internal approvals
   are needed to process this
3. Draft an internal communication
   to the relevant department head
   asking them to either confirm
   the engagement and raise a PO
   retroactively, or confirm the
   invoice should be rejected
4. Draft a holding communication
   to the vendor
5. Suggest how to document this
   as a policy exception if it
   is ultimately approved

Note: the internal communication
should make clear that this is
a policy violation and what the
correct process should have been,
but without being accusatory.

Prompt 6. Vendor Payment Status Inquiry Response

The situation: A vendor is chasing payment and you need to respond quickly with accurate status information.

This one is slightly different. It's not resolving an exception, it's handling the communication burden that exceptions create. These inquiries consume enormous AP team time and are highly formulaic.

You are an AP specialist drafting
a response to a vendor payment
status inquiry.

Details:
- Vendor name: [vendor name]
- Invoice number(s) they are
  asking about: [numbers]
- Current status of each invoice:
  [e.g. "approved, payment scheduled
  for [date]" / "in exception,
  pending GRN" / "under query,
  credit note requested"]
- Payment due date: [date]
- Any reason for delay
  (if applicable): [reason]
- Vendor contact name: [name]

Please draft a professional,
specific payment status response
that:
1. Addresses each invoice separately
   if there are multiple
2. Gives the vendor a clear expected
   payment date or next step
3. Does not over-explain internal
   processes or create unnecessary
   back-and-forth
4. Closes with a single clear action
   or confirmation statement

Keep the tone professional but warm.
This vendor relationship matters
and the response should reflect that.

Prompt 7. Partial Delivery / Disputed Invoice Amount

The situation: The vendor has invoiced for the full amount but delivery was partial. The invoice is correct from the vendor's perspective but not from ours.

You are an AP specialist handling
an invoice dispute related to
partial delivery.

Details:
- Vendor: [vendor name]
- Invoice number: [number]
- Invoice amount (full): [amount]
- Amount disputed: [amount]
- Description of what was ordered:
  [description]
- Description of what was actually
  received: [what was received and
  when, or what is still outstanding]
- PO number: [number]
- Delivery documentation available:
  [yes/no/partial]
- Has the vendor been notified
  previously: [yes/no]

Please:
1. Assess whether this should be
   handled as a partial payment,
   a credit note request, or a
   disputed invoice hold
2. Draft a vendor communication
   that clearly explains the
   delivery shortfall, specifies
   the amount we are willing to
   pay now, and requests either
   a credit note for the remainder
   or a timeline for completing
   the delivery
3. Suggest what delivery documentation
   to retain for dispute resolution
4. Note any escalation path if
   the vendor disputes our position

The vendor communication should
be factual, specific about quantities
and amounts, and avoid language
that admits liability or fault
on our side.

Prompt 8. Exception Documentation and Audit Trail

The situation: An exception has been resolved. Now you need to document it properly for the audit trail.

This is the prompt most teams skip, and it's why audit prep is painful. Consistent exception documentation takes 3 minutes with this prompt and saves hours at audit time.

You are an AP specialist creating
audit trail documentation for a
resolved invoice exception.

Details of the resolved exception:
- Exception type: [e.g. price
  discrepancy / duplicate /
  missing GRN / no PO]
- Vendor: [vendor name]
- Invoice number: [number]
- Invoice amount: [amount]
- Date exception was identified: [date]
- Date exception was resolved: [date]
- Root cause identified: [explain
  what caused the exception]
- Resolution action taken: [what
  was done to resolve it]
- Who approved the resolution: [name
  and title]
- Any credit notes or revised invoices
  received: [yes/no, reference numbers]
- Policy implications: [e.g. was
  this a one-off or does it suggest
  a process gap]

Please write a formal exception
log entry that:
1. Documents the exception clearly
   and factually
2. Records the resolution with
   enough detail for an auditor
   to understand what happened
   without needing to ask follow-up
   questions
3. Notes any process improvement
   recommendation if the root cause
   suggests a systemic issue
4. Is formatted consistently so it
   can be added to a standard
   exception register

Keep the language formal, precise,
and passive voice where appropriate
for audit documentation style.

Making This a System, Not a One-Off

Individual prompts are useful. A system is transformative.

Here's how to turn these prompts into a repeatable AP exception handling workflow:

Step 1. Build a prompt library. Create a shared document (Google Doc, Notion, Confluence, wherever your team works) with all 8 prompts saved and labelled. Everyone on the team uses the same prompts, which means consistent output and consistent documentation.

Step 2. Add your context once. At the top of your prompt document, save a "context block" that describes your organisation, your vendor policy basics, your standard payment terms, your escalation structure. Paste this at the start of any session and ChatGPT will use it as background for every prompt that follows.

For context: we are a [company type]
with [approximate vendor count] active
vendors. Our standard payment terms
are [net X]. Our AP policy requires
[key policy points]. Invoices above
[$X] require [approval level] sign-off.
Our ERP is [ERP name].

I'll be sharing invoice exception
details for you to help me investigate
and resolve. Please use this context
throughout our conversation.

Step 3. Document as you go. Use Prompt 8 at the end of every resolved exception before you close the tab. The documentation takes 3 minutes and the audit trail builds itself.

Step 4. Review monthly. At the end of each month, paste your exception log into ChatGPT and ask it to identify the most common exception types, their root causes, and whether any patterns suggest a systemic issue. The prompt:

Here is our exception log for
the past month. Please:
1. Identify the top 3 exception
   types by volume
2. Identify the most common
   root causes
3. Flag any patterns that suggest
   a systemic process gap
4. Recommend 2-3 process improvements
   that would reduce exception volume

[paste exception log]

What This Gets You, And Where the Limit Is

Used consistently, these prompts give you faster exception investigation, more professional vendor communication, better audit documentation, and a monthly insight loop that actually improves your process over time.

What they don't give you is the ability to prevent exceptions before they occur.

The prompts in this guide work on exceptions that have already happened. They make resolution faster. They don't eliminate the root causes: the informal spend commitments, the contract terms that nobody validates at invoice time, the approval chains that break down under operational pressure.

Eliminating exceptions at source requires a system that governs spend before the invoice arrives, captures informal purchase requests before commitments are made, validates invoices against actual contract terms automatically, and routes approvals based on risk rather than just amount. That's what an agentic Intake-to-Pay platform like Blackbee AI does, and why the exception queue shrinks dramatically when the full cycle is governed rather than just the invoice end of it.

But for today, copy the prompts above, build your library, and let ChatGPT take the investigation load off your team.

Frequently Asked Questions

Can I use these prompts in ChatGPT Free?

Yes, all of these prompts work in the free tier. The free version doesn't have Advanced Data Analysis, but for exception investigation and communication drafting you don't need it. Just paste your exception details into a standard chat and run the prompt.

How much context should I give ChatGPT?

As much as is relevant and as little as is unnecessary. For price discrepancies, you need the invoice amount, PO amount, contracted rate, and vendor context. You don't need to paste the full invoice text. The prompts above are designed to ask for exactly what's needed. Follow the fields listed.

Is it safe to paste invoice data into ChatGPT?

For ChatGPT Plus users, OpenAI allows you to turn off memory and opt out of training data use in Settings. For sensitive financial data, vendor names, amounts, invoice numbers, review your organisation's data governance policy before pasting real transaction data. If there's any concern, anonymise vendor names (use "Vendor A" etc.) before running the prompts. The quality of the output is not significantly affected.

Can I customise these prompts for our specific policies?

Absolutely, and you should. The prompts are designed as starting points. Add your specific approval thresholds, escalation paths, ERP field names, and policy references so the output is tailored to your operation from the start.

How do I handle an exception type that isn't covered here?

Use the base structure at the top of this guide. Describe the situation, ask for a root cause diagnosis, a resolution recommendation, the vendor communication, and the audit documentation. That framework works for any exception type.

Will this work for high-volume AP operations?

These prompts work well for exception investigation and communication, but they're manual tools. For high-volume operations processing thousands of exceptions per month, the value is in exception resolution quality and documentation consistency rather than raw speed. If exception volume is the primary challenge, the architectural solution is an agentic system that resolves exceptions autonomously, not faster manual prompting.

Ready to see what happens when exceptions get resolved autonomously rather than manually, with full reasoning documentation on every decision?

See how Blackbee AI's agentic Intake-to-Pay platform handles exception resolution

Anand Murugan is the Co-Founder and CEO of Blackbee AI, an agentic Intake-to-Pay platform that gives finance teams continuous control over every transaction, vendor, and approval. Connect on LinkedIn or visit blackbeeai.com.