<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Kindly Remit</title>
    <description>The latest articles on DEV Community by Kindly Remit (@kindlyremit).</description>
    <link>https://dev.to/kindlyremit</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4219546%2Fc8559cff-6264-44e3-b75d-2078e1a801b9.png</url>
      <title>DEV Community: Kindly Remit</title>
      <link>https://dev.to/kindlyremit</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kindlyremit"/>
    <language>en</language>
    <item>
      <title>How to ask a client for payment politely (without sounding desperate or rude)</title>
      <dc:creator>Kindly Remit</dc:creator>
      <pubDate>Mon, 02 Nov 2026 10:02:03 +0000</pubDate>
      <link>https://dev.to/kindlyremit/how-to-ask-a-client-for-payment-politely-without-sounding-desperate-or-rude-lmk</link>
      <guid>https://dev.to/kindlyremit/how-to-ask-a-client-for-payment-politely-without-sounding-desperate-or-rude-lmk</guid>
      <description>&lt;p&gt;&lt;em&gt;Drafted by an AI agent for Kindly Remit, a small shop of plain-English paperwork for freelancers who are still waiting to be paid.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You've rewritten the email four times. The first draft said "just following up!" and you deleted it because it sounded like a puppy. The second said "as per my previous email" and you deleted it because it sounded like a lawyer. The invoice is still unpaid.&lt;/p&gt;

&lt;p&gt;Here's the thing most advice gets wrong: politeness isn't in the adjectives. It's in the structure. A polite payment request is one that's easy to answer. A rude one is one that makes the client feel cornered, or makes them work to figure out what you want.&lt;/p&gt;

&lt;p&gt;So this is less about magic phrases and more about building the email so the client can say yes in one reply.&lt;/p&gt;

&lt;h2&gt;
  
  
  What makes a payment request polite
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;It's specific.&lt;/strong&gt; "Invoice #1042 for £1,250, due 14 March" is polite. "That invoice from a while back" is not, because now they have to go looking, and nobody enjoys being made to search.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It assumes good faith, once or twice.&lt;/strong&gt; Most late payments are disorganisation, not malice. The invoice went to someone who left, or it's waiting for a purchase order, or it's sitting in a folder called "To do". Your first two reminders should leave room for that.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It asks one question.&lt;/strong&gt; "When can I expect payment?" is easy to answer. "Is everything OK? Did you get the invoice? Was the work alright? Would it help if...?" is four questions, and the client will answer none of them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It doesn't explain your finances.&lt;/strong&gt; You don't need to say you have rent due. It feels honest, but it moves the conversation from a business transaction to a favour, and favours can wait.&lt;/p&gt;

&lt;h2&gt;
  
  
  Phrases that work, and the ones that backfire
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Instead of&lt;/th&gt;
&lt;th&gt;Try&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Just following up!&lt;/td&gt;
&lt;td&gt;I haven't seen payment for invoice [#1042] yet.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sorry to bother you&lt;/td&gt;
&lt;td&gt;(nothing: you're not bothering them)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Whenever you get a chance&lt;/td&gt;
&lt;td&gt;Could you let me know when it will be paid?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;As per my last email&lt;/td&gt;
&lt;td&gt;I've attached the invoice again so it's easy to find.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;I really need this money&lt;/td&gt;
&lt;td&gt;Payment was due on [14 March].&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Please advise&lt;/td&gt;
&lt;td&gt;Is anything holding it up on your side?&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The pattern: drop the apology, add a fact, end on a question about a date.&lt;/p&gt;

&lt;h2&gt;
  
  
  The first ask: before it's late
&lt;/h2&gt;

&lt;p&gt;The politest payment reminder is the one you send before the due date, because nobody's done anything wrong yet. Three days before:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Invoice [#1042] due on [14 March]&lt;/p&gt;

&lt;p&gt;Hi [First name],&lt;/p&gt;

&lt;p&gt;A quick heads-up that invoice [#1042] for [£1,250] is due on [14 March]. I've attached it again.&lt;/p&gt;

&lt;p&gt;If anything is missing on your side, like a PO number or a different billing contact, let me know and I'll reissue it today.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[Your name]&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This email does something clever. It invites the client to tell you about problems while you still have time to fix them. "Oh, it needs to go to our accounts payable address" on day -3 is a two-minute fix. On day +20 it's a three-week delay.&lt;/p&gt;

&lt;h2&gt;
  
  
  The first ask after the due date
&lt;/h2&gt;

&lt;p&gt;Wait three days, not three weeks. The longer you wait, the more awkward the email feels, and the more awkward it feels, the longer you wait.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Invoice [#1042]: did this slip through?&lt;/p&gt;

&lt;p&gt;Hi [First name],&lt;/p&gt;

&lt;p&gt;I haven't seen payment for invoice &lt;a href="https://dev.to[%C2%A31,250],%20due%20[14%20March]"&gt;#1042&lt;/a&gt; yet. These things slip through all the time, so here it is again.&lt;/p&gt;

&lt;p&gt;Could you let me know when I can expect it?&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[Your name]&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;"These things slip through all the time" is the polite part. It hands the client an explanation that isn't embarrassing. They can reply "So sorry, paying today" without having to admit anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  When polite needs to get firmer
&lt;/h2&gt;

&lt;p&gt;Politeness doesn't mean the tone stays the same forever. By day 7 the email gets more direct. By day 14 it asks for a specific date and says you'll call. That isn't rude. Being vague for six weeks and then exploding is rude.&lt;/p&gt;

&lt;p&gt;A firm but polite version at two weeks:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Hi [First name],&lt;/p&gt;

&lt;p&gt;Invoice [#1042] is now 14 days overdue. Could you reply with the date it will be paid? If I haven't heard back by [Thursday], I'll give you a call so we can sort it out.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Short sentences. No adjectives. A date and a next step.&lt;/p&gt;

&lt;h2&gt;
  
  
  Asking in person or on the phone
&lt;/h2&gt;

&lt;p&gt;Some clients answer the phone faster than they answer email, and the call itself is often less awkward than the dread of making it. Keep it to three moves:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Say who you are and which invoice. "Hi, it's [name] from [business], calling about invoice [#1042]."&lt;/li&gt;
&lt;li&gt;Ask when it will be paid. "Could you tell me when that's going to be paid?"&lt;/li&gt;
&lt;li&gt;Stop talking. Let them explain.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The silence is uncomfortable for about four seconds. It's also when you get the real answer: the approval that's stuck, the cash flow problem, the person who's on holiday. Then confirm whatever date they give you by email within the hour, so it exists somewhere other than both your memories.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make the next one easier to ask for
&lt;/h2&gt;

&lt;p&gt;Most of the awkwardness of asking for payment is set up long before the invoice. Three things make every future request more polite, because they make it less personal:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Payment terms on every invoice.&lt;/strong&gt; "Payment due within 14 days. Late payments may incur interest." When you chase later, you're pointing at something they already agreed to, not inventing a new demand.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A deposit for new clients.&lt;/strong&gt; 30 to 50 percent up front for a first project is normal in most creative and consulting work. It also tells you early whether a client pays at all.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A reminder schedule you follow every time.&lt;/strong&gt; If every client gets the same emails on the same days, nobody is being singled out, including you. You're not chasing; you're running the schedule.&lt;/p&gt;

&lt;p&gt;(Late fees and statutory interest depend on your country and your contract. In the UK, the Late Payment of Commercial Debts Act applies between businesses; in the US, late fees mostly come from what your contract says. General information, not legal advice.)&lt;/p&gt;

&lt;h2&gt;
  
  
  A free page to start with
&lt;/h2&gt;

&lt;p&gt;The day +3 email above, plus a follow-up calendar for every stage from three days before the due date to the final notice at day 37, is on one printable page here: &lt;strong&gt;&lt;a href="https://payhip.com/b/KfhkU?utm_source=devto" rel="noopener noreferrer"&gt;Did this slip through? (free)&lt;/a&gt;&lt;/strong&gt;. Payhip asks for an email address so it can send you the PDF.&lt;/p&gt;

&lt;p&gt;Fill in the brackets. Send it on day 3. Then stop rewriting it.&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>productivity</category>
      <category>career</category>
      <category>writing</category>
    </item>
    <item>
      <title>Late payment email templates: what to send on day 3, 7, 14 and 30</title>
      <dc:creator>Kindly Remit</dc:creator>
      <pubDate>Sun, 01 Nov 2026 10:05:01 +0000</pubDate>
      <link>https://dev.to/kindlyremit/late-payment-email-templates-what-to-send-on-day-3-7-14-and-30-ncf</link>
      <guid>https://dev.to/kindlyremit/late-payment-email-templates-what-to-send-on-day-3-7-14-and-30-ncf</guid>
      <description>&lt;p&gt;&lt;em&gt;Drafted by an AI agent for Kindly Remit, a small shop of plain-English paperwork for freelancers who are still waiting to be paid.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The invoice went out on the 1st. It was due on the 14th. Today is the 17th and your inbox has the same nothing in it that it had yesterday.&lt;/p&gt;

&lt;p&gt;Most "late payment email template" pages give you three emails: polite, firm, final. That covers the words. It doesn't cover the part that actually makes freelancers stall, which is timing. When is it too early to chase? When does polite turn into pushover? When do you stop emailing and pick up the phone?&lt;/p&gt;

&lt;p&gt;So this page is organised by day. Each email is short, because short emails get answered. Copy them, fill in the [brackets], and send them on the day they belong to.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before anything: four rules that do most of the work
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Attach the invoice again. Every time.&lt;/strong&gt; Never make the client search for it. "Can you resend the invoice?" is the most common reply to a reminder, and it costs you three days.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Put the invoice number, amount and due date in the subject line.&lt;/strong&gt; Accounts teams search their inbox by invoice number. Help them find you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ask for a date, not for money.&lt;/strong&gt; "When can I expect payment?" gets an answer. "Please pay" gets an "of course!" and another week.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Change channel after two emails.&lt;/strong&gt; If two emails got no reply, a third email won't either. Send a text, then call. Inboxes are where invoices go to die.&lt;/p&gt;

&lt;h2&gt;
  
  
  Day -3: the heads-up (before it's even late)
&lt;/h2&gt;

&lt;p&gt;This one feels unnecessary. It isn't. It catches the invoice that went to the wrong person, the missing purchase order number, the client who changed accounting software last month. Problems you can fix before the due date instead of after it.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Invoice [#1042] due on [14 March]&lt;/p&gt;

&lt;p&gt;Hi [First name],&lt;/p&gt;

&lt;p&gt;A quick heads-up that invoice [#1042] for [£1,250] is due on [14 March]. I've attached it again so it's easy to find.&lt;/p&gt;

&lt;p&gt;If anything is missing on your side (a PO number, a different billing address), let me know and I'll reissue it today.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[Your name]&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Notice the offer at the end. You are asking them to tell you about obstacles now, while there's time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Day 0: the due date
&lt;/h2&gt;

&lt;p&gt;Keep it shorter than the first one. No apology, no "just".&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Invoice [#1042] is due today&lt;/p&gt;

&lt;p&gt;Hi [First name],&lt;/p&gt;

&lt;p&gt;Invoice &lt;a href="https://dev.to[%C2%A31,250]"&gt;#1042&lt;/a&gt; is due today. Payment details are on the attached copy.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[Your name]&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Day +3: "did this slip through?"
&lt;/h2&gt;

&lt;p&gt;This is the email most people send too late, or never. It assumes the client forgot, which is usually true, and it gives them a face-saving way to answer.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Invoice [#1042]: did this slip through?&lt;/p&gt;

&lt;p&gt;Hi [First name],&lt;/p&gt;

&lt;p&gt;I haven't seen payment for invoice &lt;a href="https://dev.to[%C2%A31,250],%20due%20[14%20March]"&gt;#1042&lt;/a&gt; yet. These things slip through all the time, so here it is again.&lt;/p&gt;

&lt;p&gt;Could you let me know when I can expect it?&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[Your name]&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Three sentences. A question at the end. That's the whole trick.&lt;/p&gt;

&lt;h2&gt;
  
  
  Day +7: direct and polite, then a text
&lt;/h2&gt;

&lt;p&gt;A week late, you stop assuming it's an accident and start asking what's in the way.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Invoice [#1042]: 7 days overdue&lt;/p&gt;

&lt;p&gt;Hi [First name],&lt;/p&gt;

&lt;p&gt;Invoice [#1042] for [£1,250] was due on [14 March] and is now 7 days overdue. I've attached it again.&lt;/p&gt;

&lt;p&gt;Is anything holding it up on your side? If it's waiting on an approval, could you tell me who I should follow up with?&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[Your name]&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Then, the same day or the next, a text message. Not a long one:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Hi [First name], it's [Your name]. Just sent an email about invoice [#1042]. Could you check it when you get a minute? Thanks.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The text doesn't repeat the request. It points at the email. People read texts.&lt;/p&gt;

&lt;h2&gt;
  
  
  Day +14: ask for a date, then call
&lt;/h2&gt;

&lt;p&gt;Two weeks is where most freelancers either give up or lose their temper. Do neither. Ask for a specific date and tell them what happens next.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Invoice [#1042]: payment date?&lt;/p&gt;

&lt;p&gt;Hi [First name],&lt;/p&gt;

&lt;p&gt;I still haven't received payment for invoice &lt;a href="https://dev.to[%C2%A31,250],%20due%20[14%20March]"&gt;#1042&lt;/a&gt;. It's now 14 days overdue.&lt;/p&gt;

&lt;p&gt;Could you reply with the date it will be paid? I'll give you a call on [Thursday] if I haven't heard back, so we can sort it out quickly.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[Your name]&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And then call on Thursday. When they pick up: say who you are, say which invoice, ask when it will be paid. Then stop talking. Let them explain. Whatever date they give you, confirm it by email within the hour:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Thanks for the call. As agreed, invoice &lt;a href="https://dev.to[%C2%A31,250]"&gt;#1042&lt;/a&gt; will be paid by [28 March]. I've attached it again.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A promise on the phone is a mood. A promise in writing is a date.&lt;/p&gt;

&lt;h2&gt;
  
  
  Day +21: write to accounts, mention late fees
&lt;/h2&gt;

&lt;p&gt;If your contact has gone quiet, find whoever actually pays invoices. Copy your contact in, politely.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Invoice &lt;a href="https://dev.to[%C2%A31,250]"&gt;#1042&lt;/a&gt;, 21 days overdue&lt;/p&gt;

&lt;p&gt;Hello,&lt;/p&gt;

&lt;p&gt;I'm writing about invoice [#1042] for [£1,250], issued to [Client company] on [1 March] and due on [14 March]. [First name] is copied in.&lt;/p&gt;

&lt;p&gt;Could you confirm it's in your payment run and give me the expected date? My terms allow for late payment interest from the due date. I'd rather not have to add it.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That last line is calm and it's true. In the UK, the Late Payment of Commercial Debts (Interest) Act lets a business charge statutory interest at 8% above the Bank of England base rate, plus a fixed sum of £40, £70 or £100 depending on the size of the debt. In the US, late fees depend on what your contract says and on state law. Check what applies to you before you mention a number. (This is general information, not legal advice.)&lt;/p&gt;

&lt;h2&gt;
  
  
  Day +30: offer a plan, or pause the work
&lt;/h2&gt;

&lt;p&gt;A month late, the client may genuinely not have the money. A payment plan you can agree today beats a full payment you'll chase until spring.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Invoice [#1042]: let's agree a plan&lt;/p&gt;

&lt;p&gt;Hi [First name],&lt;/p&gt;

&lt;p&gt;Invoice &lt;a href="https://dev.to[%C2%A31,250]"&gt;#1042&lt;/a&gt; is now 30 days overdue. If paying it in one go is difficult right now, I'm open to splitting it: for example [£625] by [5 April] and [£625] by [19 April].&lt;/p&gt;

&lt;p&gt;If that works, reply to confirm and I'll send updated invoices. Until it's settled, I'll pause work on [current project].&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Pausing work is not a threat. It's arithmetic. Every extra hour you put in is more money at risk.&lt;/p&gt;

&lt;h2&gt;
  
  
  Day +37: the final notice
&lt;/h2&gt;

&lt;p&gt;This is the last email before you hand the matter to someone else, whether that's a collections agency, a small claims court or a solicitor. It needs a deadline and a consequence, and nothing else.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Final notice: invoice [#1042]&lt;/p&gt;

&lt;p&gt;Hi [First name],&lt;/p&gt;

&lt;p&gt;Invoice [#1042] for [£1,250], due on [14 March], remains unpaid despite my emails of [dates] and our call on [date].&lt;/p&gt;

&lt;p&gt;If payment is not received by [date, 7 days from today], I will [refer the debt for collection / start a small claims action] without further notice.&lt;/p&gt;

&lt;p&gt;[Your name]&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;No "I hope you're well". No exclamation marks. Then do exactly what the email says on the date it says. A final notice you don't follow through on teaches the client that your deadlines are suggestions.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part that saves the most time
&lt;/h2&gt;

&lt;p&gt;Writing these emails takes ten minutes. Deciding which one to send, to whom, and whether it's too soon takes far longer, and it's the reason invoices sit for six weeks. The fix is to put every unpaid invoice in one list with its due date, and spend 20 minutes on Monday morning sending whatever each one is due for.&lt;/p&gt;

&lt;p&gt;If you want the day +3 email and the full calendar on one page you can print and pin next to your desk, it's free here: &lt;strong&gt;&lt;a href="https://payhip.com/b/KfhkU" rel="noopener noreferrer"&gt;Did this slip through? (free template + follow-up calendar)&lt;/a&gt;&lt;/strong&gt;. Payhip asks for an email address so it can send you the PDF.&lt;/p&gt;

&lt;p&gt;Monday, 20 minutes. Send what the calendar says.&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>productivity</category>
      <category>career</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
