100 Best Gemini Accounts Receivable Follow-up Prompts for Bookkeepers

Direct Answer

The best Gemini prompts for accounts receivable follow-up for bookkeepers are focused, concrete prompts that guide outreach, timing, and outcomes for overdue invoices. Use clear tones, provide exact due dates and amounts, and specify output formats to ensure consistent results. Always include a payment option and a next step. Adjust placeholders for each customer and invoice.

Introduction

This page is a practical prompt library for accounts receivable follow-up tailored to bookkeepers. It provides 100 copyable Gemini prompts you can deploy directly in your AR workflow.

The prompts cover email, phone, SMS, and internal notes, with context placeholders so you can adapt them to each customer, invoice, and policy.

How to Use These Gemini Prompts

• Replace placeholders like [invoice_number], [due_date], [amount_due], [account_id], [aging_period], and [segment] with your real data before running the prompt.
• Add constraints such as tone, format, and response expectations to shape outputs.
• Request outputs in plain text or specified formats to simplify posting reminders in your AR system.
• Verify outputs by quickly checking that key facts (invoice number, amount due, due date) are correct before sending.
• When testing, run prompts on a few representative accounts to calibrate tone and timing.
• Iterate by swapping in language that matches your company policy and customer context.

100 Best Gemini Accounts Receivable Follow-up Prompts for Bookkeepers

1. Initial reminder email: You are a bookkeeper and you manage accounts receivable for a mid sized business. Your task is to draft an initial friendly reminder to a customer with outstanding invoice #[invoice_number]. Context: customer has a history of on time payments but this invoice is overdue by [days_overdue]. Include polite tone, reference the invoice number, due date, and total amount due [amount_due]. Output format: plain text email with subject line and body. Constraints: keep it under two short paragraphs, include a clear payment link, and offer payment options. Avoid aggressive language.
2. Phone reminder script: You are a bookkeeper calling a customer about an overdue invoice #[invoice_number]. Context: customer is reachable by phone and has an open balance of [amount_due] due on [due_date]. Task: deliver a concise phone script that confirms the balance, asks for a payment date, and records the call outcome. Output format: bullet list of steps and a closing action. Constraints: do not transfer the call to collections without explicit authorization, and document the response type.
3. Late payment follow up: Role: AR follow up specialist. Task: compose a late payment follow up message for invoices older than [days_overdue] days for account #[account_id]. Include account summary, aging bucket, and a single actionable request with a payment deadline. Output format: short email with a clear call to action and a payment link. Constraints: tone professional and empathetic, avoid threats.
4. Dispute resolution prompt: Role: Bookkeeper. Task: respond to a customer who raises a dispute on invoice #[invoice_number]. Context: customer claims goods not received. Provide a factual reconciliation, request supporting documents, offer to resend the goods or adjust the invoice, and propose a revised due date. Output format: structured email with sections: issue, evidence, proposed resolution, next steps. Constraints: keep to two to three paragraphs.
5. Net terms clarifier: Role: Bookkeeper. Task: clarify net terms confusion for account #[account_id]. Context: customer requested terms extensions beyond the standard net 30. Provide a clear explanation of approved terms, any fees, and revised due date. Output format: customer email with bullet points for term details. Constraints: confirm changes in writing.
6. Payment plan offer: Role: AR specialist. Task: offer a feasible payment plan for overdue invoice #[invoice_number]. Include total amount due, number of installments, frequency, interest if any, and milestone dates. Output format: structured email with a payment schedule. Constraints: ensure plan is achievable for customer and aligns with company policy.
7. Dunning sequence teaser: Role: Bookkeeper. Task: create the first teaser message in a dunning sequence for invoices aging [aging_period]. Provide a friendly reminder and a soft call to action to arrange payment. Output format: short message suitable for SMS or email subject line and body. Constraints: keep it under 100 words.
8. Aging report summary: Role: AR analyst. Task: generate a one paragraph summary of the AR aging report for account #[account_id], focusing on overdue invoices, total delinquency, and recommended next steps. Output format: plain text summary. Constraints: avoid jargon; aim for boardroom readability.
9. Escalation trigger: Role: Bookkeeper. Task: craft a trigger message to escalate an overdue invoice #[invoice_number] to collections after [days_overdue] days, including rationale, contact attempts, and required internal approval. Output format: internal note and customer message draft. Constraints: follow company escalation policy.
10. Payment option recap: Role: AR specialist. Task: prepare a concise recap of available payment options for customer with account #[account_id], including online portal, bank transfer, and card on file. Output format: customer email with a quick link list. Constraints: emphasize ease of payment and security.
11. Discount eligibility note: Role: Bookkeeper. Task: inform customer on invoice #[invoice_number] about any discount eligibility for early payment or prompt payment. Include terms, amount or percentage, and deadline. Output format: email with a single actionable line. Constraints: avoid pressuring language.
12. Recurring payer reminder: Role: AR specialst. Task: draft a recurring reminder for a customer who pays late regularly but with a good payment history previously. Include acknowledgment of timely past payments and a reminder of upcoming due date. Output format: friendly email. Constraints: set expectation for future reliability.
13. Partial payment acknowledgment: Role: Bookkeeper. Task: respond to a customer who has made a partial payment on invoice #[invoice_number]. Acknowledge receipt, show updated balance, and propose next payment date. Output format: confirmation email. Constraints: confirm remaining balance and new due date.
14. Credit memo handling: Role: AR clerk. Task: process a credit memo for invoice #[invoice_number] and communicate updated balance to customer. Output format: email with updated invoice summary and next steps. Constraints: attach or reference the credit memo number.
15. Email subject optimization: Role: Bookkeeper. Task: write 5 subject line options for overdue invoice #[invoice_number], each under 50 characters, with different angles (polite reminder, urgency, payment options). Output format: list of subject lines. Constraints: ensure not spammy.
16. SMS reminder: Role: AR agent. Task: craft a SMS reminder for overdue invoice #[invoice_number] concise and compliant with SMS best practices. Output format: short text with a single call to action and payment link. Constraints: max 160 characters.
17. Voice mail script: Role: Bookkeeper. Task: create a voicemail script for overdue invoice #[invoice_number], including your name, company, call back number, and urgency to resolve. Output format: voicemail script. Constraints: keep under 30 seconds.
18. Collector friendly tone: Role: AR coordinator. Task: rewrite a collection-friendly message for invoice #[invoice_number] that balances firmness with courtesy. Output format: email template. Constraints: avoid accusatory language.
19. International payment note: Role: Bookkeeper. Task: draft a payment reminder for an international customer with invoice #[invoice_number], listing accepted currencies and any cross border fees. Output format: email with payment options. Constraints: mention exchange rate note if applicable.
20. Tax invoice reminder: Role: AR specialist. Task: remind a customer that tax is included or excluded as appropriate for invoice #[invoice_number], and provide tax details by jurisdiction. Output format: email with tax summary. Constraints: ensure compliance.
21. Dispute deadline: Role: Bookkeeper. Task: send a reminder that a dispute window for invoice #[invoice_number] is closing soon, requesting documentation if any. Output format: email with timeline and next steps. Constraints: keep it courteous.
22. Multi-invoice follow up: Role: AR analyst. Task: draft a single message to a customer with multiple overdue invoices, listing each invoice number, amount due, and combined total. Output format: email with itemized table. Constraints: provide a single payment link for all.
23. Payment confirmation request: Role: Bookkeeper. Task: request confirmation of payment receipt for invoice #[invoice_number] once payment has been posted. Output format: short email confirming receipt and updated balance. Constraints: include expected posting date.
24. Auto payment failure note: Role: AR specialist. Task: inform customer about an automatic payment failure for invoice #[invoice_number], provide reason if known, and offer to retry. Output format: email with retry instructions. Constraints: maintain customer trust.
25. Payment reminder cadence: Role: Bookkeeper. Task: define a 3 step reminder cadence for overdue invoices aging [aging_period], with timing and suggested messaging. Output format: internal plan and customer-facing messages. Constraints: align with company policy.
26. Account balance snapshot: Role: AR analyst. Task: provide a one paragraph balance snapshot for account #[account_id], including overdue totals and next payment expectation. Output format: plain text update.
27. Goodwill gesture: Role: Bookkeeper. Task: propose a goodwill gesture for a long term customer with invoice #[invoice_number], such as a small discount or future credit, and explain rationale. Output format: email proposing the gesture. Constraints: ensure policy compliance.
28. Payment link optimization: Role: AR specialist. Task: optimize the payment link in a reminder to maximize conversions for invoice #[invoice_number]. Include a clear CTA and privacy note. Output format: email body snippet. Constraints: test two link variants.
29. Negotiation prompt: Role: Bookkeeper. Task: prepare a negotiation-friendly message for a customer requesting a payment extension on invoice #[invoice_number]. Propose a feasible new due date and any conditions. Output format: email with proposed terms. Constraints: avoid promising unapproved terms.
30. Discontinued service alert: Role: AR coordinator. Task: inform a customer that services will be suspended if invoice #[invoice_number] remains unpaid after a specified date. Output format: formal notice. Constraints: comply with legal standards.
31. Early payment incentive: Role: Bookkeeper. Task: craft a message offering a small incentive for early payment of invoice #[invoice_number], such as a one time credit if paid by a specified date. Output format: email with incentive details. Constraints: ensure terms are clear.
32. Weekend follow up: Role: AR agent. Task: draft a light weekend follow up for overdue invoice #[invoice_number] suitable for Monday morning delivery. Output format: email subject and body. Constraints: maintain professional tone.
33. Payment plan update: Role: AR analyst. Task: update an existing payment plan for account #[account_id] to reflect a changed cash flow, including updated dates and installments. Output format: internal note and customer email. Constraints: confirm agreement.
34. Invoice detail refresher: Role: Bookkeeper. Task: remind customer of invoice item details for #[invoice_number], including service description or goods, quantity, price, and tax. Output format: email with concise line items. Constraints: avoid long paragraphs.
35. Credit hold notice: Role: AR specialist. Task: inform customer that credit has been placed on hold until payment on invoice #[invoice_number] is received. Output format: email with next steps. Constraints: include contact options.
36. Payment reminder in multiple languages: Role: Bookkeeper. Task: craft the reminder for invoice #[invoice_number] in [preferred_language], ensuring key payment details and links remain clear. Output format: bilingual email. Constraints: maintain tone.
37. Dunning sequence variant: Role: AR expert. Task: create a variant of the second reminder in a 4 stage dunning sequence for overdue invoices, focusing on escalation and consequences if unpaid. Output format: email template and internal note. Constraints: comply with policy.
38. Compliance friendly reminder: Role: AR practitioner. Task: generate a reminder that cites late fees only if allowed by contract and jurisdiction for invoice #[invoice_number]. Output format: email with legal note. Constraints: avoid overreach.
39. Channel preference check: Role: Bookkeeper. Task: ask customer for preferred communication channel for future AR notices and document in account #[account_id]. Output format: short email with options. Constraints: respect privacy.
40. Proof of delivery request: Role: AR clerk. Task: request proof of delivery for invoice #[invoice_number], in case of dispute about goods received. Output format: email with document list. Constraints: keep tone neutral.
41. Partial payment schedule: Role: AR planner. Task: propose a partial payment schedule for outstanding invoices totaling [total_due] across multiple customers, with individual timelines. Output format: internal plan and customer-ready template. Constraints: align with policy.
42. Customer success note: Role: Bookkeeper. Task: craft a note that connects timely payments with customer success metrics and value received. Output format: email. Constraints: keep it constructive.
43. Remittance advice: Role: AR specialist. Task: provide remittance instructions tailored for an international customer paying invoice #[invoice_number], including bank details and reference format. Output format: email. Constraints: ensure accuracy.
44. Auto email recap: Role: Bookkeeper. Task: generate an automated recap email after a payment is posted for invoice #[invoice_number], including updated balance and next steps. Output format: system email template. Constraints: confirm posting date.
45. Dispute follow up: Role: AR agent. Task: follow up on a customer dispute for invoice #[invoice_number], requesting documentation and offering a resolution window. Output format: email with timeline. Constraints: keep it concise.
46. Chase letter with empathy: Role: Bookkeeper. Task: write a chase letter that balances empathy for the customer with urgency to collect for invoice #[invoice_number]. Output format: formal email. Constraints: avoid aggressive language.
47. Cross-sell incentive: Role: AR specialist. Task: propose a cross-sell incentive for customers paying overdue invoices to good standing for future purchases. Output format: email with offer details. Constraints: relevance to account.
48. Template customization: Role: Bookkeeper. Task: tailor a general AR reminder template for account #[account_id] to match customer segment [segment], including tone and deadline. Output format: editable template. Constraints: keep placeholders clear.
49. Legal notice draft: Role: AR manager. Task: draft a compliant legal notice for overdue invoice #[invoice_number], suitable for sending after escalation; include contact details and next steps. Output format: email template. Constraints: follow jurisdiction rules.
50. Overdue summary for client: Role: AR analyst. Task: prepare a one-page summary of all overdue invoices for a client, including totals by aging bucket and recommended actions. Output format: client-facing report. Constraints: clarity.
51. KB friendly prompt: Role: Bookkeeper. Task: create a knowledge base friendly prompt explaining how to interpret AR aging data for invoice #[invoice_number]. Output format: article snippet. Constraints: concise and actionable.
52. Friendly payment reminder: Role: AR practitioner. Task: draft a gentle payment reminder for a customer who values relationship and has a long history with the company. Output format: email. Constraints: focus on partnership.
53. Account update request: Role: Bookkeeper. Task: request updated billing contact and payment authorization for account #[account_id]. Output format: short email. Constraints: verify identity.
54. Invoice on hold notification: Role: AR clerk. Task: notify customer that invoice #[invoice_number] has been placed on hold pending payment. Output format: email with hold reason. Constraints: avoid accusations.
55. Time zone friendly: Role: Bookkeeper. Task: adjust payment reminder timing for customer in [time_zone] to align with business hours. Output format: note for scheduling. Constraints: respect local times.
56. Early response prompt: Role: AR agent. Task: craft an urgent response prompt for a customer who replies promptly to invoice #[invoice_number], confirming next steps and payment date. Output format: email response. Constraints: be decisive.
57. Refund and credit policy: Role: Bookkeeper. Task: explain refund or credit policy to a customer with outstanding invoice #[invoice_number], including eligibility and process. Output format: email. Constraints: ensure accuracy.
58. Automation handoff: Role: AR supervisor. Task: draft a note to hand off an overdue case to an automation workflow with account #[account_id], including triggers and expected outcomes. Output format: internal note and customer message template.
59. Dispute evidence checklist: Role: AR analyst. Task: provide a concise checklist of documents to support a payment dispute for invoice #[invoice_number]. Output format: bulleted list. Constraints: keep it limited to essential items.
60. Payment reminder analytics: Role: AR data analyst. Task: propose metrics to track effectiveness of reminders for invoices aging [aging_period], including response rate and payment rate. Output format: brief analytics plan.
61. Recurring customer pledge: Role: Bookkeeper. Task: request a customer pledge to maintain timely payments for future invoices after settling invoice #[invoice_number]. Output format: email. Constraints: keep it positive.
62. Attachments checklist: Role: AR clerk. Task: remind customer to attach required documents when submitting payment for invoice #[invoice_number]. Output format: email with checklist. Constraints: minimize back and forth.
63. Currency fluctuation note: Role: Bookkeeper. Task: explain potential currency fluctuation impact on invoice #[invoice_number] for a cross border payment and how it affects due date. Output format: email. Constraints: keep it simple.
64. Payment reminder template: Role: AR specialist. Task: provide a reusable reminder template for overdue invoices including placeholders for [invoice_number], [amount_due], and [due_date]. Output format: editable template. Constraints: easy to customize.
65. Customer SLA alignment: Role: Bookkeeper. Task: align AR follow up with customer service level agreement for account #[account_id], citing response times and escalation path. Output format: internal note and customer message. Constraints: ensure compliance.
66. Dispute response frame: Role: AR agent. Task: craft a calm dispute response for invoice #[invoice_number], acknowledging concerns and offering verification steps. Output format: email. Constraints: maintain helpful tone.
67. Zero balance prompt: Role: Bookkeeper. Task: compose a message for customers whose account balance has fallen to zero after payment for invoice #[invoice_number], to confirm completion and offer future support. Output format: email.
68. Payment method preference: Role: AR specialist. Task: survey customer payment method preferences for account #[account_id], and adjust reminders accordingly. Output format: email with options. Constraints: respect customer choice.
69. Late fee explanation: Role: Bookkeeper. Task: explain whether late fees apply to invoice #[invoice_number], and under what conditions. Output format: email with policy extract. Constraints: be precise.
70. Strategic discount offer: Role: AR planner. Task: propose a limited time strategic discount for overdue invoices to improve cash flow without compromising margins. Output format: email with terms. Constraints: justify impact.
71. Success story prompt: Role: Bookkeeper. Task: share a brief customer success story related to timely payments and value receipt for account #[account_id]. Output format: customer facing note. Constraints: keep it relevant.
72. Cross-border payment note: Role: AR clerk. Task: provide cross-border payment instructions for invoice #[invoice_number], including IBAN or SWIFT and any fees. Output format: email.
73. Payment reminder timing: Role: AR analyst. Task: specify optimal days of week to send reminders for invoices aging [aging_period], with rationale. Output format: internal note.
74. Disputes fast track: Role: AR manager. Task: offer a fast track for disputes on invoice #[invoice_number] with dedicated contact and response SLA. Output format: email to customer. Constraints: maintain fairness.
75. Friendly reminder thread: Role: Bookkeeper. Task: generate a short thread of three reminder messages for invoice #[invoice_number], suitable for email chain. Output format: thread text. Constraints: keep consistent tone.
76. Phone follow up cadence: Role: AR agent. Task: define a three call cadence for accounts with overdue invoices, including call objectives and scripts. Output format: internal plan and customer messages.
77. Proof of payment request: Role: Bookkeeper. Task: securely request proof of payment from a customer for invoice #[invoice_number], and provide alternative payment proof options. Output format: email.
78. Priority client note: Role: AR specialist. Task: mark a high priority client account #[account_id] and tailor follow up messaging to reflect importance. Output format: internal note and customer email. Constraints: escalate if unsatisfied.
79. Automation alert: Role: AR supervisor. Task: trigger an automation to send a reminder after a payment attempt on invoice #[invoice_number], and log the outcome. Output format: internal instruction. Constraints: ensure idempotence.
80. Credit limit check: Role: Bookkeeper. Task: remind customer about credit limit usage and how it affects their outstanding invoice #[invoice_number]. Output format: email with balance and limit details.
81. Accessibility compliant: Role: AR specialist. Task: ensure reminder content for invoice #[invoice_number] adheres to accessibility guidelines, including clear language and alternative text references. Output format: email guidelines. Constraints: meet accessibility standards.
82. Invoice notes update: Role: Bookkeeper. Task: update internal invoice notes for #[invoice_number] with new due date and customer responses. Output format: internal note. Constraints: keep concise.
83. Seasonal offer prompt: Role: AR planner. Task: propose a seasonal incentive for overdue invoices during a specific period for account #[account_id]. Output format: email with offer. Constraints: align with policy.
84. Bad debt risk warning: Role: AR analyst. Task: communicate potential bad debt risk to a supervisor for invoices aging beyond [aging_period], with recommended action. Output format: internal note.
85. Reminders in bulk: Role: AR administrator. Task: draft a bulk reminder message for a list of invoices for a client, with itemized balances and a single payment link. Output format: email template. Constraints: precise, scalable.
86. Invoice history summary: Role: Bookkeeper. Task: provide a concise invoice history summary for account #[account_id], highlighting disputes, payments, and current balance. Output format: client-facing report.
87. Payment success note: Role: AR clerk. Task: send a confirmation of successful payment posting for invoice #[invoice_number], including updated balance and next steps. Output format: email.
88. Query resolution prompt: Role: AR team member. Task: respond to a customer query about an invoice #[invoice_number] with clear, factual information and a proposed resolution. Output format: email. Constraints: avoid jargon.
89. Dashboard friendly: Role: AR analyst. Task: craft a dashboard friendly alert summary for overdue invoices aging [aging_period], suitable for exec review. Output format: plain text summary.
90. Outstanding list for calls: Role: Bookkeeper. Task: prepare a concise list of top overdue invoices requiring human outreach, with contact attempts and next actions. Output format: internal note.
91. Refund inquiry reply: Role: AR specialist. Task: respond to a customer inquiry about refunds related to invoice #[invoice_number]. Output format: email with steps and timeline. Constraints: avoid overpromising.
92. Channel cross reference: Role: AR manager. Task: map customer preferred channels to reminders for account #[account_id], and ensure consistency across channels. Output format: internal and customer messages.
93. Dispute evidence request: Role: AR agent. Task: request specific evidence for a dispute on invoice #[invoice_number], including dates, order numbers, and shipment details. Output format: email.
94. Cash flow rationale: Role: AR analyst. Task: explain how timely AR follow up improves cash flow for the company in simple terms for the customer in invoice #[invoice_number] context. Output format: email.
95. Loyalty reward note: Role: Bookkeeper. Task: offer a loyalty reward for customers who consistently pay on time over a 12 month period. Output format: email with reward details. Constraints: ensure reward is sustainable.
96. Invoice courtesy contact: Role: AR clerk. Task: initiate a courtesy contact to confirm the customer intends to pay on or before the due date for invoice #[invoice_number]. Output format: email.
97. Replacement invoice prompt: Role: Bookkeeper. Task: generate a replacement invoice for a customer due to a billing error and inform them of updated terms. Output format: email. Constraints: attach corrected invoice.
98. Account closure notice: Role: AR specialist. Task: inform customer that their account will be closed if invoices remain unpaid past a final date, while offering a resolution window. Output format: formal notice. Constraints: follow policy.
99. Final notice template: Role: Bookkeeper. Task: craft a final notice for invoice #[invoice_number] before sending to collections, including last payment deadline and consequences. Output format: email. Constraints: be professional.
100. AR best practices summary: Role: AR manager. Task: summarize best practices for accounts receivable follow up with bookkeepers for invoice #[invoice_number], including tone, timing, and channel mix. Output format: internal brief.

Best Practices

• Keep prompts as explicit as possible about tone, format, and data placeholders.
• Reuse prompts with the same structure but different account data to build a library you can scale.
• Audit prompts periodically to ensure compliance with privacy and debt collection rules.
• Store outputs in your AR system with clear tagging to track effectiveness.
• Test variations of subject lines, CTAs, and timing to improve response rates.

Common Mistakes to Avoid

• Using overly aggressive or accusatory language that damages customer relationships.
• Failing to personalize by omitting account specific details like invoice number or due date.
• Ignoring data accuracy in prompts, leading to sending wrong balances or dates.
• Not including a clear payment option or next steps in reminders.
• Overusing the same prompt across all customers without adapting to channel preferences or aging.

FAQ

What makes a Gemini prompt effective for AR follow up?

An effective prompt is specific about the invoice, due date, and amount, includes a clear call to action, offers payment options, and uses an appropriate tone for the customer.

How should I tailor prompts for different aging buckets?

Use gentler language for early reminders and firmer language for longer delays, while always including a concrete next step and a payment option.

Can prompts handle disputes?

Yes, prompts can include a dispute handling path with requests for supporting documents and a proposed resolution timeline.

What output formats work best for AR systems?

Plain text emails, structured bullet lists, and brief internal notes that can be easily copied into your AR software are most reliable.

How do I maintain compliance in prompts?

Avoid threats, respect privacy, document consent where required, and follow jurisdictional debt collection rules in all communications.

How often should I refresh prompts for best results?

Review prompts quarterly, test new wording with small sample sets, and retire underperforming variants.