The awkwardness in asking for payment is almost always caused by the words around the ask, not the ask itself. "Sorry to bother you", "just checking in", "I hope it's okay" — these aren't politeness; they're hedging. They signal that the request itself might be unreasonable. It isn't. The work was done; the payment is owed. The fix is replacing soft hedge language with direct professional language. That sounds harder than it is. Below are the specific phrasings to use and the ones to drop.
This is a craft piece — focused on the language of payment requests, not the cadence or the strategy. For the seven-stage reminder schedule and copy-paste templates or the full strategy for following up on unpaid invoices, see the related posts.
Start from the right frame: you are not asking for a favor
Most awkwardness comes from a frame mistake: treating the payment request like a favor you're asking for, rather than a contracted obligation you're following up on. The tone shifts everything. Compare these two openings:
- Favor frame: "Hi Sarah, sorry to bother you about this again — I know things get busy. I was just wondering if there's any update on invoice #042 that I sent last month? No rush, just wanted to check in!"
- Obligation frame: "Hi Sarah — following up on invoice #042 from April 18, currently 14 days past due. Could you confirm the payment date or let me know if there's a blocker? Thanks."
Both are polite. Only the second one will be paid quickly. The favor frame signals that the request might be reasonable to decline; the obligation frame doesn't. Use the obligation frame from email one onward — including the gentle, friendly emails. Friendliness and obligation are not opposites.
Phrases to drop from every payment email
- "Sorry to bother you" / "Sorry for the follow-up". You're not bothering them. They owe you money. Apologizing for the contact frames the invoice itself as the imposition.
- "Just" (as in "just wanted to check in", "just a quick reminder"). The word "just" is a hedge that signals lower importance. Cut it. "A quick reminder" reads stronger than "just a quick reminder".
- "I hope it's okay to follow up". Same problem — asks permission for an action that doesn't need permission.
- "No rush" / "whenever you get a chance" / "no pressure". These directly contradict your actual ask. The invoice is past due; there is rush. Don't say otherwise.
- "I was wondering if" / "I just wanted to ask". Preambles that delay the ask. Get to the request in sentence one.
- Excessive exclamation points. One per email is the cap. More reads as nervous, which is what you're trying not to be.
Phrases that work better than the alternatives
- "Following up on..." (instead of "sorry to bother you about...") — neutral, action-oriented, doesn't apologize for the existence of the email.
- "Could you confirm..." (instead of "I was wondering if...") — direct request for a specific action.
- "Please advise on timing" / "Please confirm the payment date". Asks for a specific output (a date) rather than vague reassurance.
- "By [SPECIFIC DATE]". "This week" is vague; "by Friday May 30" is actionable. Always include a specific date for the response.
- "If there's a blocker on your end, let me know." Opens space for the client to surface a real problem (approval delay, dispute, AP cadence) without making them confess.
- "Per our agreement..." (when invoking late fees or terms) — depersonalizes the enforcement. You're not punishing the client; the contract is.
Scripts for the three hardest moments
1. Asking a client you have a friendly relationship with
The hardest version of the ask — the client you've worked with for two years, who became a friend, who is now 21 days late. The instinct is to soften the language. Don't. The relationship is what gives you permission to be direct, not to be apologetic.
Subject: Invoice #INV-042 — 21 days overdue Hi Sarah, Following up on invoice #INV-042 ($3,400, dated April 18) — it's now 21 days past due. I haven't seen any of the usual back-and-forth so I want to make sure it's not stuck somewhere. Could you confirm by Friday whether (1) payment is in flight and when it should land, or (2) there's a blocker I can help clear? Happy to hop on a quick call if it's easier. Thanks, [YOUR NAME]
2. Asking when this is the third or fourth reminder you've sent
By the third reminder, the temptation is either to over-apologize for sending another email or to over-express frustration. Both are wrong. The right version is short, factual, and includes a documented timeline so the recipient (and anyone they forward the email to internally) can see the history.
Subject: Invoice #INV-042 — 30 days past due, no response received Hi Sarah, This is my fourth contact regarding invoice #INV-042 ($3,400, originally due April 18). Previous reminders: April 19, April 25, May 2. I have not received a response or payment commitment. Per our signed agreement, a 1.5% monthly late fee now applies — updated total is $3,451. I'd like to resolve this directly. Please reply by Wednesday May 22 with either (a) the payment date, or (b) a time we can speak by phone this week. If I don't hear back by Wednesday, I'll need to escalate to your finance team directly. Thanks, [YOUR NAME]
3. Asking on a phone call (when email has stopped working)
After Day 30-45, phone outperforms email substantially for collection. The issue is that most freelancers either avoid the call entirely or fumble it by reverting to the favor frame in person. The script below is the spine — keep it short, get a commitment with a date, document the call in writing afterward.
OPENING "Hi Sarah, it's [YOUR NAME]. I'm calling about invoice #INV-042 from April 18 — it's now 35 days past due and I wanted to talk directly since email hasn't been working." [PAUSE — let them respond. They will usually apologize or offer an explanation.] IF THEY APOLOGIZE / OFFER EXPLANATION "I appreciate that. What I need from this call is a specific date the payment will be processed. Can you commit to a date today?" IF THEY GIVE A DATE "Great — so [DATE]. I'll send you a written confirmation after this call. If anything changes before [DATE], please let me know as early as possible so we can adjust." IF THEY CAN'T GIVE A DATE "I understand. Who at the company would be the right person to talk to about the timing? I'd like to make sure we get this resolved this week." CLOSING "Thanks for taking the call. I'll send a follow-up email with what we discussed so we both have it in writing."
Tone adjustments by channel
- Email: Most formal. Subject line specificity, invoice attached, specific deadline. The default channel through Day 30.
- SMS / text message: Only if you have an existing text-message relationship with the client. "Hi Sarah — quick note that invoice #042 is past due as of May 9. Could you confirm the payment date when you're back at a computer? Thanks." Keep it brief, no attachments.
- Slack / messaging app: Same rules as SMS. Avoid for first reminder; use for escalation if the client is responsive on Slack and slow on email.
- Phone call: Best for Day 30+. Use the script above. Always follow up with email documentation of what was agreed.
- In-person (rare, but happens): If you see the client at an event or meeting, the script is: "I want to flag offline — invoice #042 is past due, can we sort out the payment date this week?" Don't pretend not to mention it; that signals it's less important than it is.
What to do if the client pushes back on the request
Three common pushbacks and the professional responses to each:
- "We don't process invoices until [date]." Acceptable answer if it's the truth and they say it proactively. Response: "Understood — can you confirm that the [SPECIFIC DATE] processing will include invoice #042? I'd like to mark my calendar to follow up if it doesn't appear by then." Lock in the date.
- "There's a problem with the invoice." Drop everything else and address the dispute directly. "What specifically needs to change?" Get the actual objection — vague "problems" are usually one of: missing line item detail, wrong PO reference, billing the wrong entity, or scope disagreement. All are fixable in <24 hours; ask for the specific issue.
- "We're not paying that." Now you have a dispute, not a late payment. Stop sending reminder emails. Move to: "I'd like to understand the specific objection. Can we schedule a 20-minute call this week to walk through it?" If the dispute is unresolvable, the next steps are mediation, collections, or small claims — but only after you've clearly documented the dispute.
The meta-rule that ties everything together
Every effective payment request — across every stage, every channel, every relationship type — does the same three things: (1) restates the specific invoice and amount, (2) asks for a specific action by a specific date, (3) doesn't apologize for the request itself. Get those three right and the email or message will land as professional regardless of whether your phrasings are perfect. Get any of them wrong and even "perfect" language won't compensate.