TL;DR: These 20 prompts draft the four-stage message ladder freelancers actually send to chase an overdue invoice — friendly, firm, escalation, final — plus payment-plan offers and a facts-then-ask structure for any of them. Every amount, date, and invoice number is an input you supply and check; none of these prompts threaten anything, and the legal rules around collections vary too much by jurisdiction to state a specific one here.
Is It Legal to Send These Payment Reminder Emails Yourself?
That caveat isn't a formality before the useful part starts — it's the actual shape of the risk here. A freelancer sending their own client a reminder about their own invoice is, in most everyday cases, doing something far less regulated than a collections agency chasing a stranger's debt on commission. But "far less regulated" is not the same as "unregulated," and exactly where the line sits is not something a generic blog post can responsibly tell you. If you're past the point of a firm-but-polite message, the honest next step is asking a professional what applies to your situation, not asking a chatbot to sound more official.
What Does a Sensible Four-Stage Reminder Ladder Look Like?
Most freelancers reach for some version of this sequence instinctively; naming the stages just makes it easier to write each one on purpose instead of guessing at the tone each time.
| Stage | Typical timing | Tone | Goal |
|---|---|---|---|
| 1. Friendly reminder | Just before or shortly after the due date | Warm, assumes oversight | Make paying easy, no pressure |
| 2. Firm follow-up | First reminder gets no reply | Direct, still professional | Restate the facts, ask for a specific reply |
| 3. Escalation | Second reminder also gets no reply | Serious, measured | Name the pattern, ask for a plan or an explanation |
| 4. Final message | Before you change how you work with this client | Plain, honest | State a real, controllable next step |
The tone escalates at every stage in this table. Nothing else does. A "final" message that arrives without a real decision behind it, or a "serious" tone that leans on a threat you can't back up, breaks the ladder's whole logic — the client can tell the difference between firmness and bluff.
How Do You Write a Friendly First Reminder?
The first reminder's entire job is to assume good faith. Most unpaid invoices are genuinely an oversight, not a refusal, and a reminder that reads as an accusation this early damages a relationship you'll probably want to keep.
1. Friendly first reminder, invoice already past due
Role: a freelancer or business owner sending a friendly first reminder about a past-due invoice.
Task: write a short, warm reminder that assumes this is an oversight, restates the invoice
details below, and makes it easy to pay.
Invoice details: [INVOICE NUMBER, AMOUNT, ORIGINAL DUE DATE — YOU SUPPLY THESE]
How to pay: [PAYMENT LINK OR METHOD]
Format: 3-4 sentences, friendly, low-pressure.
Constraints: use only the invoice details given above; if a detail isn't provided, leave a
placeholder rather than inventing a number, date, or invoice ID.
Tone: warm, assumes good faith.
What to change: paste the real invoice number and amount from your own records every time, even when it feels obvious. This is the prompt most likely to get run on autopilot, which is exactly when a wrong figure slips through unnoticed.
2. Courtesy heads-up before the invoice is even due
Role: someone sending a courtesy note before an invoice is due, not a reminder that it's late.
Task: write a brief, friendly confirmation that the invoice below is coming due soon.
Invoice details: [INVOICE NUMBER, AMOUNT, DUE DATE]
Format: 2-3 sentences.
Constraints: use only the details given; do not use any language implying the payment is
late or at risk — it isn't yet.
Tone: light, courteous, purely informational.
What to change: send this only if you already have a habit of giving clients a heads-up before due dates. Sending one for the first time on an invoice you've never done this for can read as if something's suddenly wrong, even though the note itself says otherwise.
3. First reminder to a long-standing client you want to keep
Role: someone sending a first payment reminder to a long-standing client they want to
continue working with.
Task: write a reminder that reflects the existing relationship — warmer than a first-time
client would get — while still restating the specific invoice facts and the ask clearly.
Invoice details: [INVOICE NUMBER, AMOUNT, DUE DATE]
Relationship context: [HOW LONG YOU'VE WORKED TOGETHER]
Format: 3-4 sentences.
Constraints: use only the invoice details and relationship context given; the ask must stay
specific even though the tone is warmer.
Tone: warm, personal, still clear about what's being requested.
What to change: name something specific about the relationship rather than a generic "great working with you" line. A specific detail is what makes the warmth land as genuine instead of reading as softening before the actual ask.
How Do You Write a Firmer Second Reminder When the First Gets No Reply?
A second reminder isn't just a repeat of the first at higher volume. It should name that this is a follow-up, restate the same facts so nothing is ambiguous, and ask a specific question the client can actually answer — not just resend the same soft nudge.
4. Second reminder, no reply to the first
Role: someone sending a second reminder after the first got no reply.
Task: write a firmer, still-professional follow-up that restates the invoice, notes this is
a second reminder, and asks for a specific reply.
Invoice details: [INVOICE NUMBER, AMOUNT, ORIGINAL DUE DATE]
Date first reminder was sent: [DATE]
Format: 3-4 sentences, ends with a specific, answerable question (e.g. "can you confirm
payment by [DATE], or let me know if there's an issue with the invoice").
Constraints: use only the details given; do not add urgency language beyond stating this is
the second reminder; do not imply any consequence.
Tone: direct, professional, no longer purely friendly.
What to change: always give the exact date the first reminder went out. A vague "I followed up last week" invites debate about timing; a dated one doesn't, and it gives you a clean record if a third message ends up being necessary.
5. Second reminder that rules out a problem with the invoice itself
Role: someone following up on an unpaid invoice who wants to rule out an issue on the
client's end before assuming it's simply late.
Task: write a follow-up that asks plainly whether there's a problem with the invoice itself
(wrong amount, missing details, needs to be resent) alongside the payment reminder.
Invoice details: [INVOICE NUMBER, AMOUNT, DUE DATE]
Format: 3-4 sentences, includes a direct question about whether the invoice is correct.
Constraints: use only the details given; treat "something's wrong with the invoice" as a
genuine possibility, not a rhetorical question.
Tone: practical, assumes there could be a real reason.
What to change: run this before assuming a client is simply avoiding payment. A wrong PO number or a misspelled billing contact genuinely stops some invoices before anyone even sees them, and ruling that out costs you nothing.
6. Second reminder addressed to accounts payable instead of your usual contact
Role: someone sending a second reminder to a company's accounts-payable contact rather than
their usual day-to-day contact.
Task: write a reminder addressed to the accounts-payable contact below, referencing the
invoice and noting who to loop in if it's not their responsibility.
Invoice details: [INVOICE NUMBER, AMOUNT, DUE DATE]
AP contact (if known): [NAME, OR "ACCOUNTS PAYABLE TEAM"]
Usual contact's name: [FOR REFERENCE IN THE EMAIL]
Format: 3-4 sentences.
Constraints: use only the names and details given; do not assume a reason for the delay.
Tone: professional, slightly more formal than a note to a day-to-day contact.
What to change: loop your usual contact into this email too, even briefly, rather than going around them silently. Copying accounts payable without their knowledge can read as an escalation aimed at them personally, which usually isn't what you mean by it.
How Do You Escalate the Tone Without Threatening Anything?
This is the stage where it's easiest to overcorrect into language that sounds like a threat. Naming the pattern factually — two reminders sent, no response — carries its own weight without needing to reach for legal or credit language that may not even be true yet.
7. Third reminder that names the pattern factually
Role: someone sending a third reminder after two previous reminders went unanswered.
Task: write a message that states the pattern factually (two reminders sent, dates, no
response) and asks for a specific plan or explanation, with no implied threat.
Invoice details: [INVOICE NUMBER, AMOUNT, ORIGINAL DUE DATE]
Prior reminder dates: [DATES OF THE FIRST TWO REMINDERS]
Format: 4-5 sentences, states the pattern plainly, then asks a direct question.
Constraints: never mention legal action, a collections agency, or credit reporting, even as
a hypothetical; state only what has and hasn't happened, not what might happen next.
Tone: serious, measured, factual — firm without being adversarial.
What to change: list the exact dates of both prior reminders, not just "twice before." Specific dates make the pattern harder to dispute and easier for the client to check against their own inbox.
8. Third reminder that directly asks if there's a dispute
Role: someone who wants to rule out a genuine dispute before escalating further.
Task: write a message asking plainly whether there's a dispute about the work, the invoice,
or the amount, and inviting the client to say what it is if so.
Invoice details: [INVOICE NUMBER, AMOUNT]
Format: 3-4 sentences, includes a direct, non-defensive question about a possible dispute.
Constraints: use only the details given; do not assume there is or isn't a dispute — ask.
Tone: open, non-defensive, genuinely inviting a response.
9. Rewrite a frustrated draft into something you can actually send
Role: an editor rewriting a frustrated draft third reminder into something professional.
Task: rewrite the draft below to keep the facts and the ask, removing any language that
reads as a threat, an implied legal consequence, or a credit-reporting reference.
Draft: [PASTE YOUR FRUSTRATED DRAFT]
Format: same length or shorter, same facts, no threatening language.
Constraints: strip any phrase implying legal action, a collections agency, credit reporting,
or a consequence you cannot actually back up; keep the specific facts and the ask.
Tone: firm, factual, professional.
What to change: if this prompt keeps stripping out the same phrase every time you run it, that's worth noticing on its own. A habit of reaching for language you have to keep deleting usually means it's time to decide what you'd actually do next, rather than keep writing around it.
How Do You Draft an Honest Final Message?
A message that uses the word "final" needs to mean something, or the next client who ignores three reminders and gets a fourth learns that "final" is negotiable. Decide what you're actually willing to do before you write a message that implies you've decided.
10. Final message stating a real, controllable consequence
Role: someone sending a final message before changing how they work with a non-paying client.
Task: state the facts (invoice, amount, how overdue, prior reminders), then state, factually
and without threatening language, what you are actually going to do on your side.
Invoice details: [INVOICE NUMBER, AMOUNT, HOW OVERDUE]
Prior reminders sent on: [DATES]
What you're actually doing: [A REAL, CONTROLLABLE STEP — E.G. PAUSING FURTHER WORK,
WITHHOLDING A DELIVERABLE, REQUIRING PREPAYMENT ON FUTURE WORK]
Format: a short message — facts first, then the stated step, then how the client can resolve it.
Constraints: state only a consequence you control and have already decided on; never imply
legal action, a collections agency, or a credit-reporting consequence unless that is genuinely
already underway and true.
Tone: plain, honest, not adversarial.
What to change: name a consequence you can actually carry out starting the day you send this. A stated step you quietly don't follow through on teaches the client that your "final" messages are negotiable, which undoes the whole point of the ladder for next time.
11. Final message when you haven't decided what happens next
Role: someone sending a final payment chase who hasn't yet decided what to do if it's ignored.
Task: state the facts plainly and ask for a specific response by a specific date, without
stating any next step, because none has been decided yet.
Invoice details: [INVOICE NUMBER, AMOUNT, HOW OVERDUE]
Format: a short message ending in a specific, dated ask.
Constraints: do not invent or imply a consequence that hasn't actually been decided; a plain
"please respond by [DATE]" is honest, an implied threat with no plan behind it is not.
Tone: plain, direct.
What to change: use this version honestly, not as a way to sound serious without actually committing to anything. If you already know what you'll do next, the version above naming a real consequence is the more honest choice.
12. List your realistic next steps before you write anything client-facing
Role: someone deciding what "final" actually means before sending a final payment chase.
Task: given the situation below, list the realistic next steps actually available, for your
own planning — do not draft anything to send to the client.
Situation: [HOW OVERDUE, HOW MANY REMINDERS SENT, WHAT YOU'RE ACTUALLY WILLING TO DO]
Format: a short bulleted list of realistic options, internal use only.
Constraints: list only options genuinely available to you — pausing further work, requiring
prepayment, writing off the balance, or consulting a professional about formal collection or
legal options; do not draft client-facing language in this prompt.
Tone: internal, practical.
What to change: actually write this list down somewhere, even three lines in a notes app. The point is to have decided before you're mid-draft on the client-facing version and reaching for whatever sounds firm in the moment.
How Do You Offer a Payment Plan Without It Reading as Desperate?
A payment plan reads as a solution when it's specific, and as a concession when it's vague. Naming exact installment amounts and dates does more for how confident the offer sounds than any wording choice does.
13. Draft a payment plan offer
Role: someone offering a payment plan for an overdue invoice.
Task: write a message proposing the payment plan below as a way to resolve the balance.
Invoice details: [INVOICE NUMBER, TOTAL AMOUNT OWED]
Proposed plan: [NUMBER OF INSTALLMENTS, AMOUNTS, DATES — YOU SUPPLY THESE]
Format: a short message stating the balance, the proposed plan, and asking for confirmation.
Constraints: use only the plan terms given; do not calculate or invent installment amounts
or dates yourself.
Tone: solution-oriented, not punitive.
What to change: keep the installment count realistic for what the client has actually proposed being able to manage, not whatever clears the balance fastest. A plan the client can't keep is worse than a longer one they actually complete.
14. Respond to a client-proposed payment plan
Role: someone responding to a client's own proposed payment plan for an overdue invoice.
Task: write a reply that either accepts the plan below as proposed, or asks for one specific
adjustment, based on the decision you input.
Client's proposed plan: [WHAT THEY PROPOSED]
Your decision: [ACCEPT AS-IS, OR THE ONE ADJUSTMENT YOU WANT]
Format: 3-4 sentences.
Constraints: use only the decision given; do not negotiate terms the prompt wasn't told to
negotiate.
Tone: cooperative, clear.
What to change: if you're pushing for one adjustment, name the specific term you want changed rather than a general "can we revisit this" — a vague pushback on a plan someone already offered tends to read as reluctance rather than a real counter-proposal.
15. Confirm a verbally agreed payment plan in writing
Role: someone documenting a payment plan that was agreed verbally (a call or meeting) so
there's a written record.
Task: write a confirmation email restating the agreed plan below for the record.
Agreed plan: [WHAT WAS AGREED — INSTALLMENTS, AMOUNTS, DATES]
Format: a short message restating the plan and asking the client to confirm it matches
their understanding.
Constraints: use only the agreed terms given; do not add a term that wasn't part of the
verbal agreement.
Tone: neutral, record-keeping.
What to change: send this the same day the call happens, while both sides remember the same numbers. A confirmation sent a week later is exactly the kind of message that surfaces a disagreement about what was actually agreed.
How Do You Match Tone for a Client You Want to Keep vs One You're Letting Go?
The facts in a payment chase barely change between these two cases. The tone should change a lot, and deciding which one applies before you draft anything saves you from writing a warm message to a relationship that's already over, or a cold one to a client you'd genuinely like to keep past this invoice.
16. Reminder tone for a client you want to keep long-term
Role: someone chasing payment from a client they want to keep working with long-term.
Task: write a reminder that's firm about the ask but preserves the relationship, referencing
the working history below.
Invoice details: [INVOICE NUMBER, AMOUNT, HOW OVERDUE]
Relationship context: [HOW LONG, WHY YOU WANT TO KEEP THE RELATIONSHIP]
Format: 3-4 sentences.
Constraints: use only the details given; the ask must still be specific and dated even
though the tone is warmer.
Tone: warm but clear, relationship-preserving.
What to change: the relationship context you supply matters more here than the invoice details do — a generic "we've worked together a while" produces a generic-sounding reminder, while a specific project or a real length of time is what actually reads as warm.
17. Reminder tone for a relationship you're ending regardless
Role: someone chasing a final payment from a client they don't intend to work with again.
Task: write a message that's plain and businesslike, with no attempt to preserve warmth,
while still avoiding any threat or implied legal language.
Invoice details: [INVOICE NUMBER, AMOUNT, HOW OVERDUE]
Format: 3-4 sentences.
Constraints: do not include relationship-preserving language that isn't genuine; do not add
threatening or legal language even though the relationship is ending.
Tone: plain, businesslike, neither warm nor hostile.
What to change: resist the urge to explain why the relationship is ending in this particular message. That belongs in a separate conversation, if it happens at all — this one has exactly one job, which is getting paid.
18. Decide which tone actually fits before you draft anything
Role: someone deciding which tone fits a specific overdue-invoice situation before drafting
the reminder itself.
Task: given the situation below, state whether a relationship-preserving tone or a plain
businesslike tone fits better, and why, in one or two sentences.
Situation: [WHETHER YOU WANT TO KEEP THIS CLIENT, HOW THE RELATIONSHIP HAS GONE SO FAR]
Format: a one-line recommendation with a one-sentence reason.
Constraints: this prompt recommends a tone only; it does not draft the reminder itself.
Tone: n/a — this is a decision-support prompt.
How Do You Split a Payment Chase Into Facts, Then the Ask?
Almost every message on this page benefits from this one structural move: state what's true, then ask for exactly one thing. A payment chase that blends the explanation and the request into one paragraph makes the ask easy to skim past, which is the opposite of what a message asking for money should do.
19. Split a messy draft into facts, then the ask
Role: an editor restructuring a payment-chase message into two clear parts.
Task: rewrite the draft below as two parts — the facts (invoice, amount, how overdue, what's
already been sent), stated plainly, then a single specific ask.
Draft: [PASTE YOUR DRAFT]
Format: two short parts, facts then ask, not literal headers in the final email.
Constraints: move nothing beyond what's already in the draft; the ask must be a single,
specific, dated request, not several bundled together.
Tone: matches the original draft, just restructured.
What to change: this works on any message on this page, not just a payment chase written from scratch — run it on a reply you already sent once, if you're not sure it actually landed with a clear ask attached.
20. Turn rough notes about a non-paying client into a clean facts-then-ask email
Role: someone turning rough notes or a voice-memo transcript about a non-paying client into
a clean, sendable email.
Task: from the rough notes below, write a short facts-then-ask email — what's owed, how
overdue, what's already been sent, then one specific ask.
Rough notes: [YOUR UNSTRUCTURED NOTES OR TRANSCRIPT]
Format: facts first, then a single ask, 4-6 sentences total.
Constraints: use only the figures and dates present in the rough notes; if an amount or date
is unclear, mark it [CONFIRM] rather than guessing.
Tone: calm, factual, professional.
What to change: transcribe the rough notes honestly, including the parts where you're not sure of the exact figure. The [CONFIRM] marker is doing real work here — losing it because the notes felt "close enough" is exactly how a wrong number ends up in a message asking someone for money.
If the overdue amount is tangled up with a dispute about what the contract actually says, our contract-review prompts include a payment-terms extraction prompt built for exactly that, with the same rule about never stating what a clause legally requires. For the invoice itself, our proposal-to-invoice templates cover the earlier stages of a client engagement, from scope to the invoice note that goes out the first time, before any of this reminder ladder is needed. The broader freelancer prompt library covers the rest of the client relationship this page doesn't touch. And our companion piece on escalations and difficult customers covers the mirror-image conversation — when the difficult message is coming at you about your own work, rather than the other way around.
Does the Free Plan Cover This?
Yes, for occasional use. Every prompt above is plain text — copy it, fill in the brackets with your own verified figures, and run it in ChatGPT, Claude, or Gemini exactly as written, no extra tool required. Prompt Architects is an optional layer that turns the role/task/format/constraints/tone structure into a sidebar you fill in, inside the chat you already have open.
The Free plan includes 5 prompt enhancements per day, forever, no credit card required, per the FAQ page — enough to draft a reminder or two on a day you're chasing several invoices at once. What Free doesn't include: saving these as reusable templates, or a personal context library to store your standard invoice format and payment terms once instead of retyping them into every prompt. Those are Pro-plan features, priced at the time of writing on /pricing; check the current figure there, since it's running a launch discount that won't last. For what it's worth, our own refund policy runs the same direction as the advice on this page: a 14-day money-back guarantee on paid plans, stated plainly on that page rather than something you'd have to chase us to honor.
Stop rewriting prompts. Start shipping.
Works with ChatGPT, Claude, Gemini, Grok, Midjourney, Ideogram, Veo3 & Kling. 4.8★ on the Chrome Web Store.
Create An AccountNone of this replaces the actual decision at the center of a payment chase: what you're genuinely willing to do if it keeps getting ignored, and whether this situation has crossed from "write a firmer email" into "talk to a professional about your actual options." What it replaces is staring at a blank reply box, unsure whether the third reminder this month should sound different from the first, and writing something either too soft to work or too sharp to be safe to send.