These prompts help busy AP professionals draft vendor emails, payment notices, and dispute communications instantly. Copy any prompt, fill in your details, and get professional emails ready to send.
These prompts pair well with Jasper AI for Finance-specific tone control, or Copy.ai for fast iteration.
Payment Delay and Issue Communications
You are an accounts payable specialist notifying a vendor about a payment delay.
Vendor: {vendor_name} Invoice number: {invoice_number} Original due date: {original_due_date} New expected payment date: {new_payment_date} Delay reason: {reason: system_upgrade / cash_flow / approval_delay / documentation_issue} Payment amount: {payment_amount} Vendor relationship: {long_term / new / critical_supplier} Urgency level: {routine / urgent / critical}
Write a 150 to 200 word professional email explaining the payment delay. Open with acknowledgment of the original due date and immediate transparency about the delay. Provide the specific new timeline and reason without over-explaining company internal issues. Close with a direct contact for questions and assurance about future payments. Use a tone that maintains vendor relationship trust while being factual about the situation.
When to use it: When your payment run is delayed and you need to proactively communicate with vendors before they start calling.
Pro tip: Send this email 2-3 days before the original due date when possible. Vendors appreciate early communication over last-minute notifications.
You are an AP manager responding to a vendor’s urgent payment inquiry about an overdue invoice.
Vendor: {vendor_name} Invoice number: {invoice_number} Days overdue: {days_overdue} Amount: {invoice_amount} Payment status: {in_queue / pending_approval / investigating_discrepancy / check_issued} Issue found: {no_PO_match / pricing_discrepancy / missing_receipt / duplicate_invoice / none} Expected resolution: {specific_date_or_timeframe} Vendor tone in inquiry: {professional / frustrated / threatening}
Write a 200 to 250 word response email that addresses their concern directly. Start by acknowledging the overdue status and their inquiry. Explain the current status clearly and what specific action you’re taking. If there’s an issue, state exactly what’s needed from them. Provide a firm timeline for resolution and your direct contact. Match their urgency level while maintaining professional composure.
When to use it: When a vendor emails or calls asking “Where’s my payment?” and you need to respond same-day with specifics.
Pro tip: Always include the next action step, even if it’s “I will email you by Friday with an update.” Vendors want to know when they’ll hear from you again.
You are an accounts payable clerk requesting additional documentation to process a payment.
Vendor: {vendor_name} Invoice number: {invoice_number} Invoice date: {invoice_date} Amount: {invoice_amount} Missing items: {receipt / signed_contract / PO_number / tax_documentation / delivery_confirmation} Deadline for submission: {deadline_date} Payment timeline after receipt: {payment_timeframe} Previous requests sent: {first_request / second_request / final_request} Vendor payment terms: {net_30 / net_15 / due_on_receipt}
Write a 180 to 220 word email requesting the missing documentation. Open by referencing the invoice specifically. List exactly what’s needed in bullet format for clarity. Explain how this impacts their payment timeline without sounding punitive. Provide clear submission instructions (email, portal, fax). Include a specific deadline and what happens if documents aren’t received. Close with contact information for questions.
When to use it: When invoices are stuck in your approval workflow because vendors didn’t include required backup documentation.
Pro tip: Include your fax number and email in the signature. Some older vendors still prefer fax for sensitive documents, and accommodating this speeds up the process.
You are an AP specialist notifying a vendor that their invoice has been rejected and needs correction.
Vendor: {vendor_name} Invoice number: {invoice_number} Rejection reason: {pricing_error / wrong_billing_address / incorrect_PO / duplicate_submission / service_not_delivered} Specific error details: {detailed_description_of_issue} Correct information: {what_should_be_corrected_to} Resubmission method: {email / vendor_portal / mail} Expected reprocessing time: {timeframe_after_correction} Original amount: {original_amount} Vendor contact history: {responsive / slow_to_respond / new_vendor}
Write a 200 to 240 word email explaining the invoice rejection clearly and constructively. Start with the invoice reference and direct statement that it’s being rejected. Explain the specific issue found and what needs to be corrected. Provide clear resubmission instructions and timeline expectations. Avoid blame language while being firm about requirements. End with your direct contact for questions about the correction needed.
When to use it: When three-way matching fails or invoices have errors that prevent payment, and you need the vendor to resubmit correctly.
Pro tip: Screenshot the error or attach the original invoice with markup when possible. Visual explanation prevents back-and-forth emails about what needs fixing.
You are an accounts payable manager explaining payment terms changes to an existing vendor.
Vendor: {vendor_name} Current payment terms: {current_terms} New payment terms: {new_terms} Effective date: {effective_date} Reason for change: {cash_flow_management / system_standardization / company_policy / vendor_volume_change} Impact on next payment: {will_affect / will_not_affect} Next scheduled payment: {payment_date_and_amount} Vendor relationship duration: {years_working_together} Alternative options available: {early_pay_discount / other_arrangements / none}
Write a 250 to 300 word email announcing payment terms changes professionally. Open by acknowledging your working relationship. Clearly state the change and effective date upfront. Explain the business reason briefly without extensive justification. Detail how this affects their next payment cycle. Offer to discuss the change if they have concerns. Close by reaffirming the business relationship and providing direct contact for questions.
When to use it: When your company changes standard payment terms and you need to notify vendors before the change takes effect.
Pro tip: Send this 30-45 days before implementation, not right before the change. Vendors need time to adjust their cash flow planning.
Vendor Setup and Onboarding
You are an AP coordinator welcoming a new vendor and explaining payment processes.
Vendor: {vendor_name} Vendor contact: {primary_contact_name} Services/products provided: {what_they_supply} Payment terms agreed: {net_30 / net_15 / other} Invoice submission method: {email / portal / mail} Required documentation: {W9 / insurance_certificates / contracts / other} First invoice expected: {timeframe} AP contact person: {your_name_and_direct_contact} Vendor portal access: {available / not_available / being_setup}
Write a 280 to 320 word welcome email that sets up the vendor for success. Start with a professional welcome and confirmation of their vendor status. Clearly explain your invoice submission process and requirements. List required documentation they need to provide before first payment. Explain payment timing and method. Provide your direct contact and encourage questions. Include next steps for them to complete setup. Use a welcoming but businesslike tone that establishes professional expectations.
When to use it: Right after a new vendor is approved in your system and they need to understand your AP processes before sending their first invoice.
Pro tip: Include examples of properly formatted invoices if your company has specific requirements. This prevents delays on their first few submissions.
You are an AP clerk requesting updated vendor information for compliance requirements.
Vendor: {vendor_name} Information needed: {updated_W9 / new_banking_details / insurance_renewal / address_change / contact_update} Current information on file: {what_you_currently_have} Compliance deadline: {deadline_date} Consequence of non-compliance: {payment_hold / vendor_deactivation / audit_issue} Submission method: {secure_email / vendor_portal / certified_mail} Previous request attempts: {first_request / follow_up / final_notice} Vendor payment volume: {high / medium / low} Last update received: {date_of_last_update}
Write a 200 to 250 word email requesting updated vendor information for compliance. Open by explaining what specific information needs updating and why. Reference compliance requirements without getting into complex regulations. Provide clear submission instructions and deadline. Explain what happens if information isn’t received by deadline. Make it easy by listing exactly what they need to send. Close with your direct contact for questions and assistance with the update process.
When to use it: When annual compliance reviews show outdated vendor information, or when vendors notify you of changes that require documentation.
Pro tip: Send these requests in batches by month rather than all at once. Spreading compliance updates across the year prevents overwhelming your inbox with responses.
You are an accounts payable specialist setting up electronic payments for a vendor who currently receives checks.
Vendor: {vendor_name} Current payment method: {check / wire / other} Proposed new method: {ACH / wire / virtual_card / other} Monthly payment volume: {average_monthly_amount} Information needed: {banking_details / ACH_authorization / wire_instructions} Security requirements: {encryption / secure_portal / phone_verification} Timeline for changeover: {target_date} Benefits to mention: {faster_payment / reduced_processing / environmental} Vendor tech comfort level: {high / medium / low}
Write a 240 to 280 word email proposing electronic payment setup. Start by explaining the benefits of electronic payments for their business. Outline what information you need from them and how you’ll protect it. Explain the changeover timeline and process. Address common concerns about electronic payments proactively. Provide clear next steps and your direct contact for setup questions. Use language that makes the change sound advantageous rather than mandatory.
When to use it: When you’re converting check payments to electronic methods and need vendor cooperation to gather banking information.
Pro tip: Mention specific benefits like “payments arrive 3-5 days faster than checks” rather than generic advantages. Vendors respond better to concrete improvements.
You are an AP manager notifying a vendor about vendor portal access and training.
Vendor: {vendor_name} Portal name: {portal_system_name} Login credentials: {being_sent_separately / included / vendor_creates_own} Portal capabilities: {invoice_submission / payment_status / document_upload / reporting} Training session: {scheduled_date_time / self_guided / on_demand} Mandatory usage date: {date_when_required} Support contact: {portal_support_contact} Current submission method: {email / mail / fax} Vendor size/complexity: {large_volume / small_vendor / mid_size}
Write a 220 to 260 word email introducing vendor portal access and encouraging adoption. Start by announcing portal availability and key benefits for their business. Explain main features they’ll use most often. Detail how to access training and get login credentials. Provide timeline for when portal use becomes required. Address the transition from their current method. Include support contact information and reassurance about help during transition. Use encouraging tone that frames this as an improvement for them.
When to use it: When rolling out vendor portal access and you need vendors to start using self-service features instead of calling AP.
Pro tip: Schedule portal training sessions in small groups by vendor size. Large vendors need different features than small ones, and targeted training improves adoption.
You are an accounts payable coordinator requesting vendor banking verification for fraud prevention.
Vendor: {vendor_name} Verification trigger: {routine_audit / payment_method_change / security_protocol / suspicious_activity} Information to confirm: {bank_name / routing_number / account_number / account_type} Verification method: {callback_to_known_number / secure_email / certified_letter} Payment hold status: {payments_held / payments_continuing / next_payment_affected} Security concern level: {routine_verification / heightened_security / fraud_investigation} Vendor relationship: {long_term_trusted / newer_vendor / recent_changes} Timeline for response: {timeframe_needed}
Write a 180 to 220 word email requesting banking information verification for security purposes. Open by explaining this is routine security verification, not accusation of wrongdoing. State exactly what information needs confirmation. Explain your verification process and why it’s necessary. Provide clear instructions for how they should respond. If payments are held, explain when they’ll resume after verification. Reassure them this protects both parties. Include your direct contact and expected response timeframe.
When to use it: When your fraud prevention protocols require banking verification, or when vendor information changes trigger security reviews.
Pro tip: Always call from your main office number when verifying banking changes. Vendors are increasingly aware of fraud and will verify you’re legitimate before providing sensitive information.
Payment Status and Inquiry Responses
You are an AP specialist responding to a vendor’s request for payment status on multiple invoices.
Vendor: {vendor_name} Invoices requested: {invoice_numbers_and_amounts} Status of each invoice: {paid / processing / pending_approval / on_hold} Payment dates for processed ones: {dates_when_paid_or_will_be_paid} Issues with pending ones: {specific_problems_or_none} Next payment run date: {next_scheduled_payment_date} Total amount in question: {total_dollar_amount} Vendor inquiry tone: {routine_check / concerned / urgent} Your relationship: {regular_communication / infrequent_contact / new_relationship}
Write a 250 to 300 word comprehensive response covering all invoices mentioned. Start by thanking them for the inquiry and confirming you’re reviewing their account. Address each invoice individually with specific status and timeline. Group similar statuses together for clarity. If any invoices have issues, explain what’s needed to resolve them. Provide your next communication date if any items are still pending. Close with direct contact information and willingness to discuss further.
When to use it: When vendors send monthly reconciliation requests or ask about status on several invoices at once.
Pro tip: Copy your response format into a template and save it. Multi-invoice status requests are common and having a consistent format saves time while looking professional.
You are an accounts payable clerk explaining why a vendor’s invoice is on hold and what they need to do.
Vendor: {vendor_name} Invoice number: {invoice_number} Hold reason: {three_way_matching_issue / approval_needed / pricing_dispute / missing_documentation / budget_approval} Specific problem: {detailed_explanation_of_issue} Vendor action needed: {resubmit_documents / contact_project_manager / revise_pricing / wait_for_approval / none} Internal action needed: {budget_approval / manager_sign_off / receipt_matching / other} Expected resolution timeframe: {specific_timeframe} Invoice amount: {amount} Alternative contact: {project_manager / department_head / other}
Write a 200 to 240 word explanation email that clearly communicates the hold reason and next steps. Start by acknowledging their invoice and stating it’s currently on hold. Explain the specific issue in plain language without internal jargon. Clearly state what action, if any, they need to take. Explain what you’re doing internally to resolve it. Provide realistic timeline for resolution. If they need to contact someone else in your organization, provide that contact information. Close with reassurance that you’re working to resolve it.
When to use it: When vendors call asking about invoices that have been sitting in your system for longer than normal payment terms.
Pro tip: If the hold is due to internal approvals, give vendors the approval person’s contact information. This takes pressure off AP and often speeds up resolution.
You are an AP manager confirming payment details after a vendor reports they haven’t received payment.
Vendor: {vendor_name} Invoice number: {invoice_number} Payment amount: {payment_amount} Payment method: {check / ACH / wire / virtual_card} Payment date issued: {date_payment_was_sent} Check number or transaction ID: {specific_payment_identifier} Mailing address used: {address_where_sent} Bank details used: {bank_information_if_electronic} Days since payment issued: {number_of_days} Next action needed: {stop_payment / reissue / investigate / wait}
Write a 180 to 220 word email confirming payment details and next steps for a missing payment. Start by acknowledging their concern about missing payment. Provide specific payment details including date, amount, and method. Give them the check number or transaction reference for their records. Confirm the address or bank information used. Explain next steps you’ll take to investigate or reissue. Provide timeline for resolution and your direct contact for follow-up. Reassure them you’re taking immediate action.
When to use it: When vendors claim they never received a payment that shows as issued in your system.
Pro tip: Include the check number or ACH trace number in your response. Vendors can use this to investigate on their end, which sometimes reveals the payment was received but not properly applied.
You are an accounts payable coordinator explaining payment timing for a rush payment request.
Vendor: {vendor_name} Invoice number: {invoice_number} Rush reason: {vendor_cash_flow / project_urgency / past_due_oversight / supplier_demand} Normal payment timeline: {standard_processing_time} Earliest possible payment: {rush_payment_date} Rush payment method: {expedited_check / same_day_wire / emergency_ACH} Additional fees: {wire_fees / expedite_charges / none} Approval needed: {manager_approval / standard_process} Invoice amount: {payment_amount} Vendor urgency level: {critical / important / preferred}
Write a 190 to 230 word response about rush payment possibilities and process. Start by acknowledging their urgent need for payment. Explain your normal timeline briefly. Detail what rush options are available and associated timeframes. If there are additional fees, explain these clearly. State what approvals or processes are needed for rush payment. Provide specific timeline for when they can expect payment. If rush isn’t possible, explain why and give firm timeline for normal processing. Close with direct contact for status updates.
When to use it: When vendors request expedited payment due to cash flow issues or urgent project needs.
Pro tip: Keep a list of rush payment fees handy (wire charges, overnight mail costs). Vendors often agree to rush processing when they understand the timeline and costs involved.
You are an AP specialist providing payment confirmation and remittance details after payment has been issued.
Vendor: {vendor_name} Payment amount: {total_payment_amount} Payment date: {date_payment_was_issued} Payment method: {check / ACH / wire / virtual_card} Reference number: {check_number_or_transaction_id} Invoices included: {invoice_numbers_and_individual_amounts} Deductions taken: {discount_amount / adjustment_amount / none} Reason for deductions: {early_pay_discount / credit_memo / pricing_adjustment / none} Expected delivery/posting: {when_vendor_should_receive_payment} Contact for payment issues: {your_direct_contact}
Write a 160 to 200 word payment confirmation email with complete remittance details. Start by confirming payment has been issued and the total amount. Provide payment method and reference number. List each invoice included in the payment with individual amounts. If any deductions were taken, explain these clearly with reasoning. Give expected delivery or posting timeline. Include your contact information for any payment questions. Keep tone professional and informative, providing all details they need for their records.
When to use it: When vendors request payment confirmation, or proactively when sending large payments or payments with multiple invoices.
Pro tip: Send these confirmations automatically for payments over your company’s threshold (like $10,000). Large payments warrant proactive communication to prevent follow-up calls.
Dispute Resolution and Problem Communications
You are an AP manager addressing a pricing dispute on a vendor’s invoice.
Vendor: {vendor_name} Invoice number: {invoice_number} Disputed amount: {amount_in_question} Invoice total: {total_invoice_amount} Contract price: {agreed_contract_rate} Invoice price: {price_vendor_charged} Supporting documentation: {contract_section / purchase_order / email_agreement} Undisputed portion: {amount_not_in_dispute} Payment plan for undisputed: {will_pay_partial / hold_entire_invoice} Previous discussions: {none / email_trail / phone_conversations} Resolution deadline needed: {timeframe_for_resolution}
Write a 260 to 300 word email addressing the pricing dispute professionally but firmly. Start by referencing the specific invoice and noting the pricing discrepancy. Clearly state the agreed-upon price and cite your supporting documentation. Explain the difference between contract price and invoiced amount. Offer to pay any undisputed portion while resolving the dispute. Request their explanation of the pricing difference and supporting documentation. Provide timeline for resolution and your direct contact. Maintain professional tone while being clear about contractual obligations.
When to use it: When vendor invoices don’t match contracted rates and you need to resolve the discrepancy before payment.
Pro tip: Always cite specific contract sections or PO numbers. This moves the conversation from “he said/she said” to document-based resolution, which resolves faster.
You are an accounts payable coordinator rejecting a duplicate invoice submission.
Vendor: {vendor_name} Duplicate invoice number: {invoice_number} Original invoice number: {original_invoice_if_different} Original payment date: {when_original_was_paid} Payment method: {how_original_was_paid} Payment reference: {check_number_or_transaction_id} Amount: {invoice_amount} Services/goods covered: {what_the_invoice_was_for} Reason for duplicate: {vendor_error / system_issue / unclear} Vendor submission method: {email / mail / portal}
Write a 170 to 210 word email explaining the duplicate submission and providing original payment details. Start by identifying the invoice as a duplicate submission. Reference the original invoice and payment details clearly. Provide specific payment information (check number, payment date, method) for their records. Suggest they check their records or payment application process. Offer to send payment confirmation or documentation if needed. Ask them to verify if there’s something different about this submission that makes it not a duplicate. Close with willingness to investigate if they believe there’s an error.
When to use it: When vendors resubmit invoices that you’ve already paid, either by mistake or because they haven’t applied your payment correctly.
Pro tip: Attach a copy of the original payment stub or remittance advice when possible. Visual proof prevents back-and-forth emails about whether payment was really made.
You are an AP specialist responding to a vendor’s complaint about consistently late payments.
Vendor: {vendor_name} Payment terms: {agreed_payment_terms} Recent payment delays: {how_many_days_late_typically} Reason for delays: {approval_bottlenecks / cash_flow / processing_issues / vendor_compliance} Specific examples: {recent_invoices_that_were_late} Improvement plan: {process_changes_being_made} Timeline for improvement: {when_changes_take_effect} Interim measures: {what_youre_doing_now} Vendor relationship importance: {critical