AI Prompts for Late Payment Follow-ups

The invoice is sent. The due date passes. A week goes by. Then two.

Most freelancers know what comes next: a reluctance to follow up that turns into avoidance, then anxiety, then a message that either sounds too aggressive or too apologetic. Writing a payment reminder feels confrontational. It is not. Sending a reminder is professional behavior, not rudeness. But that knowledge does not make the writing any easier.

This is exactly where AI earns its place. The discomfort of chasing late payments is not really about the money. It is about the words. What do you say? How do you say it without damaging the relationship? How firm is too firm? AI removes that barrier. You no longer have to sit with a blank email draft, overthinking the tone. You paste a prompt, fill in the context, and get a usable message in seconds.

According to a GoCardless survey, 42% of small business owners feel uncomfortable chasing payments for outstanding invoices. The two reasons cited most often: fear of coming across as rude and fear of upsetting the client. AI does not experience either of those fears. It gives you the draft. You review, adjust, and send.

This page is a prompt library. It covers every stage of the follow-up sequence, plus prompts for handling excuses, writing subject lines, refining drafts, and adapting messages for other channels.

What Makes a Good AI Prompt for This Use Case

Generic input produces generic output. “Write a payment reminder email” gives you a corporate-sounding template that could belong to any business in any industry. It will not get paid faster.

Context changes everything. The AI needs to know: who the client is to you, what the invoice is for, how many times you have already followed up, what tone fits this relationship, and whether there are any circumstances worth acknowledging. Provide those details, and the output shifts from a bland template to a message that reads like you wrote it.

Every prompt in this library uses the same pattern: role or relationship context, specific invoice details you fill in, desired output format, and a tone instruction. Once you understand that pattern, you can build your own prompts for situations not covered here.

Prompt Set 1: Friendly Reminder (1–3 Days After Due Date)

The due date has passed. You have not heard anything. The most likely explanation: the client forgot, or the invoice got buried. A gentle, professional nudge resolves most late payments at this stage.

Prompt 1A: For an Ongoing Client Relationship

Use this when the client has paid you before and you have an established working relationship.

You are helping a freelancer write a professional payment reminder email.

Context:

• Client name: [CLIENT NAME]
• Invoice number: [INVOICE NUMBER]
• Invoice amount: [AMOUNT]
• Original due date: [DUE DATE]
• Days overdue: 1–3
• Relationship: ongoing, we have worked together multiple times
• Previous reminders sent: none
• Tone: warm, friendly, assumes it was a simple oversight

Write a short reminder email (no more than 5 sentences). Include the invoice number, amount, and due date. Offer to resend the invoice if needed. End with a clear but friendly call to action.

Expected output: A brief, conversational message that treats the late payment as an oversight rather than a problem. Check that the AI has not used threatening language or created unnecessary urgency at this early stage.

Prompt 1B: For a Newer Client

Use this when the client is relatively new and you want to be professional without assuming familiarity.

You are helping a freelancer write a professional payment reminder email.

Context:

• Client name: [CLIENT NAME]
• Invoice number: [INVOICE NUMBER]
• Invoice amount: [AMOUNT]
• Original due date: [DUE DATE]
• Days overdue: 1–3
• Relationship: newer client, we have completed one or two projects together
• Previous reminders sent: none
• Tone: professional and courteous, not overly casual

Write a concise reminder email (no more than 5 sentences). Reference the invoice number, amount, and due date. Offer to answer any questions about the invoice. Include a clear call to action.

Expected output: A polished, neutral message that introduces the reminder without familiarity or coldness. Check that it does not read like an automated payment notice, which can feel impersonal to a newer client you are still building a relationship with.

Prompt Set 2: Firmer Reminder (7–10 Days After Due Date, No Response)

No payment. No reply. The invoice is now 7–10 days overdue and your first message has gone unanswered. The tone shifts: still professional, still solution-focused, but with more directness. Vague language creates room for delay. Specific language closes it.

Prompt 2A: Following Up With No Response Received

You are helping a freelancer write a professional follow-up payment reminder.

Context:

• Client name: [CLIENT NAME]
• Invoice number: [INVOICE NUMBER]
• Invoice amount: [AMOUNT]
• Original due date: [DUE DATE]
• Days overdue: [7–10]
• Previous reminders sent: 1 (sent [DATE OF FIRST REMINDER])
• Response received: none
• Tone: professional and direct, still respectful, increased urgency without aggression

Write an email (no more than 7 sentences) that:

1. References the unanswered first reminder
2. States clearly that payment is now [X] days overdue
3. Asks the client to confirm receipt and provide a payment timeline
4. Offers two options: pay now via [PAYMENT METHOD] or reply to arrange a brief call
5. Keeps the door open for communication

Expected output: A message that escalates the urgency without accusation. It should read as firm and businesslike. Check that it offers a clear path forward rather than just restating the problem.

Prompt 2B: Client Responded But Has Not Paid

Sometimes a client acknowledges the invoice but the payment does not come. That response is progress. It is also a new baseline: they know, they confirmed, and they still have not paid.

You are helping a freelancer write a follow-up email for a client who responded to a previous reminder but has still not made payment.

Context:

• Client name: [CLIENT NAME]
• Invoice number: [INVOICE NUMBER]
• Invoice amount: [AMOUNT]
• Original due date: [DUE DATE]
• Days overdue: [X]
• Client response: they acknowledged the invoice but gave no firm payment date (or said they would pay by [DATE] and did not)
• Tone: professional, direct, solution-focused

Write an email (no more than 7 sentences) that:

1. Acknowledges their previous reply
2. Notes that payment has not yet arrived
3. Asks for a specific payment date, not an open-ended commitment
4. Reattaches or references the invoice for convenience
5. Keeps the tone respectful but makes clear this needs to be resolved promptly

Expected output: A message that holds the client accountable to their own acknowledgment without sounding combative. Check that it asks for a specific date rather than an open-ended “as soon as possible.”

Prompt Set 3: Formal Notice (14–21 Days After Due Date)

At this point, you have followed up more than once. The invoice is now two to three weeks overdue. This is a formal notice: professional, direct, and explicitly referencing what happens next if payment does not arrive.

Prompt 3: Formal Notice With Late Fee Reference

You are helping a freelancer write a formal payment notice.

Context:

• Client name: [CLIENT NAME]
• Invoice number: [INVOICE NUMBER]
• Invoice amount: [AMOUNT]
• Original due date: [DUE DATE]
• Days overdue: [14–21]
• Previous reminders sent: [NUMBER], most recent on [DATE]
• Late fee clause: [YES state the terms, e.g., “1.5% per month after 14 days overdue” OR NO omit late fee reference]
• Tone: formal, professional, no warmth expected at this stage but not hostile

Write a formal notice email that:

1. States clearly that the invoice is [X] days overdue
2. References all previous follow-up attempts
3. Specifies a payment deadline of 5 business days from the date of this email
4. If applicable: states that a late fee of [AMOUNT/PERCENTAGE] will apply or has already been applied
5. Requests written confirmation of payment intent by [SPECIFIC DATE]
6. Closes professionally without threats, but with clarity about next steps if unresolved

Expected output: A short, formal message that reads like a final notice. It should not read as aggressive, but it should leave no room for further delay. Check that the late fee clause, if applicable, is phrased accurately according to your actual terms.

Prompt Set 4: Responding to Client Excuses

Client excuses follow patterns. Most of them are not malicious. Some are genuine. All of them require a response that moves toward resolution rather than simply acknowledging the excuse. The prompts below handle the four most common scenarios.

Prompt 4A: Client Says “I Forgot”

You are helping a freelancer respond to a client who says they forgot to process payment.

Context:

• Client name: [CLIENT NAME]
• Invoice number: [INVOICE NUMBER]
• Invoice amount: [AMOUNT]
• Days overdue: [X]
• Client’s message: they apologized and said they forgot, no specific payment date given
• Tone: understanding but clear, request a specific commitment

Write a reply (no more than 5 sentences) that:

1. Accepts the explanation without dwelling on it
2. Provides the payment link or bank details again for convenience
3. Asks them to confirm a specific date by which payment will be made
4. Keeps the tone warm but forward-moving

Expected output: A brief reply that treats the excuse as resolved and moves directly to action. Check that it does not over-reassure or let the client off the hook without a concrete commitment.

Prompt 4B: Client Says “My Client Hasn’t Paid Me Yet”

A client’s cash flow problem is their problem, not yours. That does not mean you cannot be empathetic. It does mean you still need a payment plan or a firm date.

You are helping a freelancer respond to a client who says they are waiting on payment from their own client.

Context:

• Client name: [CLIENT NAME]
• Invoice number: [INVOICE NUMBER]
• Invoice amount: [AMOUNT]
• Days overdue: [X]
• Client’s message: they explained that their own client has not paid them yet and they are waiting on funds
• Tone: empathetic but firm, focused on reaching a concrete agreement

Write a reply (no more than 7 sentences) that:

1. Acknowledges their situation briefly without accepting it as an indefinite excuse
2. Proposes one of the following: a partial payment now with the remainder by a specific date, OR a written payment schedule with firm dates
3. Sets a deadline for their response to this proposal
4. Keeps the tone professional and solution-oriented

Expected output: A response that demonstrates understanding without creating an open-ended deferral. Check that it proposes a specific solution rather than leaving the timeline vague.

Prompt 4C: Client Says “I’ll Pay Next Week” Getting a Written Commitment

Verbal commitments disappear. A written commitment on record is a different thing entirely.

You are helping a freelancer respond to a client who has verbally committed to paying “next week” but without a specific date.

Context:

• Client name: [CLIENT NAME]
• Invoice number: [INVOICE NUMBER]
• Invoice amount: [AMOUNT]
• Client’s message: they said they will pay next week but gave no specific date
• Tone: positive, professional, anchoring the commitment in writing

Write a brief reply (no more than 4 sentences) that:

1. Confirms you have noted their commitment to pay next week
2. Asks them to confirm the specific date of payment (e.g., “Could you confirm if that means payment by [SPECIFIC DATE]?”)
3. States that you will follow up if payment has not arrived by that date
4. Keeps the tone friendly the goal is to lock in a date, not to escalate

Expected output: A short message that turns a vague commitment into a named date. Check that it does not feel accusatory. The prompt is designed to feel like confirmation, not a challenge.

Prompt 4D: Client Claims There Is a Dispute Requesting It in Writing

A dispute raised verbally or informally after an invoice is overdue is different from a dispute raised at delivery. Either way, you need it documented before responding.

You are helping a freelancer respond to a client who has raised a dispute about the invoice or the work delivered.

Context:

• Client name: [CLIENT NAME]
• Invoice number: [INVOICE NUMBER]
• Invoice amount: [AMOUNT]
• Client’s message: they have raised a concern or dispute about [briefly describe: e.g., “the number of hours billed” or “the quality of a specific deliverable”]
• Tone: calm, professional, not defensive, focused on resolution process

Write a reply (no more than 7 sentences) that:

1. Acknowledges that you have received their concern
2. Requests that they put the specific dispute in writing (email is fine) so you have a clear record of what needs to be addressed
3. Confirms you will respond once you have their written details
4. Does not admit fault, concede the invoice, or make any financial adjustments in this message
5. Keeps the tone professional and cooperative

Expected output: A holding message that requires the client to formalize the dispute before you respond to it. Check that the AI has not included any language that could be read as admitting liability or agreeing to reduce the invoice.

Prompt Set 5: Subject Lines

Subject lines determine whether the email is opened. A vague subject line gives a client room to deprioritize. A clear one removes that option.

Prompt 5: Generate Subject Line Options

Generate 5 subject line options for a payment reminder email at the following stage.

Context:

• Stage: [e.g., “Stage 2 no response to first reminder” or “Stage 3 formal notice”]
• Invoice details: Invoice #[NUMBER] for [AMOUNT], now [X] days overdue, for [brief description of work, e.g., “brand identity design” or “website copywriting”]
• Desired tone: [e.g., “professional and direct, not aggressive” or “firm but not alarming”]

Requirements:

• Each subject line should be under 10 words
• At least two options should name the invoice number directly
• At least one option should create mild urgency without sounding threatening
• Avoid generic phrases like “following up” or “just checking in”

Expected output: Five distinct subject lines with different approaches: some specific, some relational, some urgency-framed. Check that none reads as spam-flaggable or aggressive. Pick the one that fits the client relationship.

Prompt Set 6: Adjusting an AI-Generated Draft

The first draft is rarely the final one. These prompts are for refining AI output, not generating from scratch. They are for the common cases where the AI wrote something close but not quite right.

Prompt 6A: Make It More Direct Without Being Aggressive

I have a payment reminder email draft. Rewrite it to be more direct and clear without increasing the aggression or formality.

Specific changes needed:

• Remove any hedging language (e.g., “I just wanted to,” “I hope this finds you well,” “I was wondering if”)
• Make the request for payment explicit in the first two sentences
• Shorten the email to [TARGET LENGTH, e.g., “4 sentences”]
• Keep the tone professional and respectful

Here is the draft: [PASTE DRAFT HERE]

Expected output: A tighter, more direct version of your draft. Check that it still sounds like a person wrote it, not a collections notice.

Prompt 6B: Shorten to 3 Sentences

Condense the following payment reminder email to exactly 3 sentences without losing the essential information.

The 3 sentences must include: the invoice reference and amount, the fact that payment is overdue, and a clear next step or call to action.

Here is the draft: [PASTE DRAFT HERE]

Expected output: A three-sentence message suitable for use as a short follow-up or a secondary message after a longer first reminder. Check that the invoice details are still present and the call to action is clear.

Prompt 6C: Add a Reference to the Late Payment Clause Without Sounding Threatening

Revise the following payment reminder email to include a brief, professional reference to my late payment clause.

Clause details: [e.g., “My terms include a 1.5% monthly late fee for invoices unpaid after 14 days, as stated in the contract signed on [DATE]”]

Requirements:

• Reference the clause once, in one sentence
• Do not make it sound like a threat
• Position it as a factual statement, not a consequence being imposed
• Keep the rest of the email unchanged

Here is the draft: [PASTE DRAFT HERE]

Expected output: The original email with one sentence added that references the late fee clause factually and without alarm. Check that the added sentence does not change the tone of the rest of the message.

Prompt Set 7: Multi-Channel Variations

Not every follow-up is an email. Some clients respond faster on WhatsApp. Some relationships warrant a phone call. These prompts convert existing messages into shorter formats or generate talking points for a call.

Prompt 7A: Convert an Email to a Short WhatsApp or LinkedIn Message

Convert the following payment reminder email into a short WhatsApp (or LinkedIn) message.

Requirements:

• Maximum 3 sentences
• Keep the invoice number and amount
• Maintain a professional but conversational tone
• End with one clear action: either pay now via [PAYMENT LINK] or reply to confirm a date
• Do not include a formal greeting or closing signature

Here is the email: [PASTE EMAIL HERE]

Expected output: A short, direct message suitable for a messaging app. Check that it does not start with “Hi, hope you’re well” or any social opener that reduces the impact of the reminder.

Prompt 7B: Generate Talking Points for a Phone Follow-Up

Generate talking points for a brief phone call to follow up on an overdue invoice.

Context:

• Client name: [CLIENT NAME]
• Invoice number: [INVOICE NUMBER]
• Invoice amount: [AMOUNT]
• Days overdue: [X]
• Relationship: [brief description, e.g., “longstanding client” or “new client, second project”]
• Goal of the call: get a specific payment commitment or understand what is blocking payment
• Tone: professional, calm, direct

Provide 4–5 talking points in plain language (not a script). Include: how to open the conversation, how to state the purpose without being awkward, what to ask for specifically, and how to close the call with a defined next step.

Expected output: A brief set of bullet points you can glance at during the call. Check that the opening does not treat the call as a casual catch-up the purpose should be clear from the first 20 seconds.

Using AI Output: What to Do With the Draft

AI drafts are starting points, not finished messages. Three things to do before you send.

First, add the specific details the AI cannot know: the exact invoice number, the precise amount, the correct due date, and your actual payment method or link. AI fills these with placeholders. Replace every one of them.

Second, adjust the personal touch. One sentence of personal context transforms an AI draft into something that reads like you. A reference to the project you worked on together, an acknowledgment of a conversation you had last week, a note about the next deliverable you have in progress: any of these tell the client this is a message from a person, not a system.

Third, read it aloud before sending. If a sentence makes you pause, the client will too. Trim it or rewrite it until it reads naturally.

AI handles the structure and the tone calibration. You handle the relationship.

Send Smarter, Get Paid Faster

AI prompts make late payment follow-up faster and less uncomfortable. If you would prefer to skip manual follow-up entirely, Ruul sends automatic payment reminders based on your invoice due dates. No prompts needed.

Invoice clients in 190 countries with no company required. Ruul acts as the Agent of Record: you send the invoice, Ruul handles the legal and financial process, and you get paid within 1 business day after the client pays. Automatic reminders run in the background, so the follow-up happens whether or not you remember to send it.

If managing tax records alongside your invoices is part of your workflow, Ruul’s organized document storage keeps everything in one place. And if you work with recurring clients on retainer, subscription billing through Ruul removes the manual invoicing step entirely.

For freelancers invoicing internationally, multiple payout currencies mean you receive payment in the currency that works for you, including USDC for crypto payouts if that fits your setup.