How-to guide · Getting paid

How to ask for late payment professionally

By the WorkKitly Team · Last updated: November 2026 · 8 min read

To ask for a late payment professionally, assume an oversight before you assume anything else: send a short, courteous note restating the invoice number, the amount and the original due date, attach the invoice again, and make paying easy. Then escalate in stages on a fixed schedule — a polite reminder in the first week, a firm follow-up at two weeks, a final notice at thirty days, and a phone call beyond forty-five days — each step shorter, calmer and more specific than the one before. This guide walks the whole ladder, with example wording for every stage.

The ladder: five stages, in order

Chasing works when it runs on a schedule rather than on emotion. One message per stage, sent once, then silence until the next date — a client who hears from you exactly when promised takes the next message seriously. The wording blocks below are deliberately short; WorkKitly's late payment email generator takes the same stages and produces the full emails with your details filled in, ready to copy and send.

Stage 1: Before the due date — the friendly heads-up

Goal: get the invoice in front of the right person before it can be lost, so a missing invoice is never the problem. Tone: pure service — no hint of a chase, because nothing is late yet. Send it two or three days before the due date, or with the delivery email.

Hi [Name] — sending invoice 2026-041 for $1,080 ahead of its due date on 17 November, attached again for convenience. The payment details are on the invoice itself. If your accounts team needs anything else from me, now is a good time to ask.

Stage 2: 1–7 days overdue — the polite reminder

Goal: surface the oversight and make paying the easiest next click. Tone: light and warm, written as if the money is certainly coming — because at this stage it almost always is. State the facts once: number, amount, due date.

Hi [Name] — a quick note that invoice 2026-041 for $1,080 was due on 17 November, and I have not seen it arrive yet. I have attached it again in case the original went astray. Could you let me know once it is in the payment run?

Stage 3: 14 days overdue — the firm follow-up

Goal: a specific answer — a payment date, or the name of whatever is blocking it. Tone: businesslike and shorter; courtesy without padding. Ask one direct question, then stop.

Hi [Name] — invoice 2026-041 for $1,080 is now two weeks past its due date of 17 November. Please confirm the date it will be paid — or tell me what is holding it up, so we can clear it this week.

Stage 4: 30 days overdue — the final notice

Goal: set a deadline and state the one consequence you will genuinely carry out — usually pausing work, which is covered below. Tone: formal and brief. This should be the shortest email of the five; length reads as room to negotiate.

Hi [Name] — invoice 2026-041 for $1,080, due 17 November, remains unpaid despite my earlier notes. Please arrange payment by [date]. If it is still outstanding after that date, I will pause work on the current project until the account is settled, as set out in our agreement.

Stage 5: 45+ days — the phone call, then formal steps

Goal: speak to a human. Email has had five weeks; the problem is now either money or avoidance, and an inbox cannot tell you which. Tone on the call: calm and factual — state the facts, then listen more than you talk.

Hi [Name], I am calling about invoice 2026-041 for $1,080, which was due on 17 November. I have sent a few emails without hearing back, so I wanted to agree with you directly today how this gets settled.

Confirm whatever is agreed by email the same day — date, amount, method — so the promise exists in writing. If the call produces nothing, the remaining steps are formal: a letter before action, mediation, or a small-claims route where one exists, in proportion to the sum. That is general guidance, not legal advice; for a significant amount, a short consultation with a lawyer or debt adviser is usually money well spent.

What every chase email should include

Whatever the stage, every message carries the same five facts — what an accounts team needs to act without replying with a question:

  • The invoice number — the reference their system searches by.
  • The amount due, with the currency.
  • The original due date — and, from the firm stage on, how many days overdue the invoice now is.
  • How to pay — bank details or a payment link, repeated in full, never "as before".
  • The invoice itself, attached again. Never assume the original survived their inbox.

One more line earns its place at the later stages: the specific ask. "Please confirm it is in Friday's payment run" gets an answer; "please advise" gets a shrug. And if the invoice that went out was missing any of this in the first place, fix that too — the checklist of what to include on a freelance invoice covers the fields whose absence stops a payment before chasing ever starts.

Late fees: only what was agreed, said carefully

A late fee works as a term only when the client agreed to it before the work started — in the signed proposal, the contract, or terms they accepted. Raised for the first time in a chasing email, it is not a term but a new demand, and clients treat it that way: it becomes the thing they argue about instead of the invoice. If you did agree one, there is no need to threaten with it — just restate it as arithmetic:

As set out in the proposal approved on [date], a late fee of [X]% per month applies to invoices unpaid after the due date. With that fee, the balance on invoice 2026-041 now stands at $[amount].

Two cautions. Late-fee rules, caps and enforceability vary by country and by type of client, so treat this as general guidance, not a legal statement, and check what applies to your business before relying on a fee. And going forward, put the clause where it belongs — before the job starts. Our proposal generator includes a late-fee clause in the terms it drafts, which is the version of this conversation that never has to happen over email.

Pausing work: when, and how to say it

Pausing ongoing work is the one consequence most freelancers can actually carry out, which is why it belongs in the final notice — and only there. Announce it in advance, in the notice itself, with a date: a pause that arrives as a surprise reads as retaliation, while a pause announced in advance reads as a term being applied. Keep it narrow — pause the current project, not the whole relationship — and restart promptly the day payment lands, saying so when you do.

I will pause work on [project] from [date] until invoice 2026-041 is settled, and restart as soon as payment lands.

And never announce a pause you will not carry out. One consequence that turns out to be empty teaches the client to discount every future one.

When they reply: keep the relationship

Most chases do end with a reply, and how you handle the reply is part of the ladder too — the aim is a client who pays and stays.

A new date. Thank them, repeat the date back in writing, and diary it. The confirmation is not bureaucracy; it turns a vague assurance into a commitment you can point to: "Thanks — noted, payment on 5 December. I will check again on the 6th if it has not landed." Then do exactly that, once.

A partial payment. Accept it graciously, and confirm the rest in writing straight away: the amount received, the balance remaining, and the date agreed for it. A part payment does not restart the ladder at stage one — pick up where you left off, schedule intact, one step firmer in tone only if the new date is missed too.

A dispute about the work. Separate it from the money that is not in dispute: ask for the undisputed part to be paid on schedule and deal with the disputed item on its own track, so an argument about one deliverable holds nothing else hostage.

Keep the records

From the first invoice onward, keep one folder per client: the proposal or contract with the payment terms, the invoice exactly as sent, delivery or sign-off evidence, every chase email with its date, and a short note of any phone call — date, who you spoke to, what was agreed. You will probably never open it again. But if a payment ever becomes a formal dispute, that calm, dated trail is your evidence — and it is far easier to keep as you go than to reconstruct later.

Questions

For a large invoice, before the due date — a heads-up two or three days ahead costs nothing, and the invoice can never later be described as never received. After the due date, send the first real reminder within the first week: most late payments at that stage are oversights, and a prompt, polite note is normal practice, not pushiness.
Once per stage — five touches across roughly six weeks, each on a date announced in the previous message. Three emails in a week read as panic; one that arrives exactly when promised carries weight. If the fifth touch — the phone call — produces nothing, more emails rarely do; that is when to consider the formal routes.
You can ask, but the client never accepted the term, so expect it to be disputed rather than paid — and the argument often delays the original amount too. The reliable route is upstream: a late-fee clause in the proposal or contract, agreed before work starts. Rules vary by country, so check what applies to you.
Through the early stages, usually yes — most delays are process failures, and goodwill is worth keeping while the ladder is young. By the final notice, at around thirty days, pausing is a normal, professional step: announce it in advance with a date, keep it to the current project, and restart the day payment lands.

Related: the wording, ready to send

This guide is the strategy; the late payment email generator is the same ladder as finished emails — polite reminder, firm follow-up and final notice, with your invoice details filled in and ready to copy. If a chase uncovers a problem with the invoice itself — a missing reference, no payment details — rebuild it cleanly with the invoice generator and resend it the same day. And next time, let the proposal put the terms in writing before the work starts, so the ladder is a reminder, not an invention.