Free · no email required

How to Ask a Client for Payment — Politely, Then Firmly

Most late payments are not refusals. They are invoices that never entered the approval queue. That changes what you should send, and when.

Below is the schedule an overdue invoice should follow, the two emails that do most of the work, and the mistakes that make an invoice read as optional.

Not legal advice. I'm not a lawyer. For anything high-value or heading toward a formal claim, take advice in your jurisdiction.

The schedule

The ladder below is the whole method. Each rung has a job, and skipping rungs is what turns a late invoice into an old one.

WhenSendTonePurpose
Day 0 — with the invoiceInvoice deliveryNeutralLand the terms while goodwill is highest
3 days before duePre-due nudge belowHelpfulCatch the approval queue before it's late
Due dateDue todayNeutralRemove "I didn't realise"
Due + 3Gentle chase belowFriendlyAssume an oversight, because it usually is
Due + 7FirmBusinesslikeName the late fee. Ask for a payment date
Due + 14EscalateFormalNew recipient, work suspended
Due + 30Final noticeFormalState what happens next, with a date
Due + 40Letter before actionLegalThe last document before you act

The pre-due nudge is the one that matters most and the one nearly everyone skips. An email three days before the due date costs nothing and prevents most of the ladder below it from ever being needed.

Two rules hold for the whole sequence:

  1. Never skip a rung, never stall on one. Predictability is the pressure. A client who learns that day 7 always brings a firmer email starts paying on day 6.
  2. Every email restates the amount, the invoice number, and the due date. The person who eventually pays you is often not the person you have been emailing, and they need those three facts without scrolling.

Three days before it's due

Subject: Re: Invoice [INV-2026-014] · due [Friday]

Hi [NAME],

Quick heads-up that invoice [INV-2026-014] for [$1,440] is due [this Friday, 6 Sep].

Nothing needed if it's already scheduled — just flagging it in case it needs to go through approvals first.

[YOUR NAME]

Reply in the same thread, not a new one. The whole ladder should be one thread: by the escalation stage you want a single scroll that shows every reminder you sent.

Three days after it's due — the polite chase

This is the email most people are looking for when they search for a polite way to ask. Note what it does not do: it does not apologise, and it does not ask for money. It offers an excuse and asks for a routing.

Subject: Re: Invoice [INV-2026-014] · now 3 days overdue

Hi [NAME],

I don't think payment has come through for invoice [INV-2026-014] ([$1,440], due [6 Sep]). I'm assuming it's slipped through a gap rather than anything else.

Could you confirm it's in the payment run, or point me to whoever handles AP if it's easier for me to chase it there?

Re-attaching the invoice for convenience.

[YOUR NAME]

"Point me to whoever handles AP" is the workhorse sentence. It gives an embarrassed contact an easy, face-saving action, and it gets you the name of the person who can actually release money. Ask for it early.

When polite stops working

At about a week overdue the request has to change shape. Stop asking for payment and start asking for a date.

A request for a date is much harder to leave unanswered than a request for money, and once someone commits to a date in writing, the next email writes itself. This is also where you mention the interest your contract already provides for — mention it, not apply it. The threat is a lever; the charge is a small amount of money that costs you the lever.

Past two weeks, the recipient changes. Accounts payable or your contact's manager, with your original contact copied in — not blind-copied, because the point is that they can see it — and work suspended until it clears.

What not to do

What actually prevents this

Ranked by how much late payment each one removes:

  1. Take a deposit. Nothing else comes close. A client who has paid 40% up front behaves differently for the whole project.
  2. Don't hand over the final asset until the final payment clears — deployment, source files, account transfer. This turns collection from a request into a condition.
  3. Invoice the day the milestone is accepted. Every day you delay invoicing is added to the payment cycle, and it comes off the end.
  4. Send the pre-due nudge. Three days early, every time, no exceptions.
  5. Get the AP contact and the PO requirement at kickoff, not at day 25.
  6. Make it trivially easy to pay you. Correct bank details, the invoice number as the reference, no currency the client has to convert by hand.
  7. Charge new clients Net 14. Offer Net 30 as a reward for a good payment history, and say so out loud — it turns your terms into something they earn.

Before the invoice: the contract

Two clauses decide how this whole page goes. If ownership transfers on payment rather than on delivery, an unpaid invoice is their problem. If payment isn't contingent on their client paying them, "we can't pay until we get paid" stops being an argument.

→ 13 clauses to strike from a client's contract — free, no email.

Sending the invoice itself

There's a free invoice generator here that runs from a single HTML file — no account, no server, and it keeps working with the network off.

→ Offline Invoice Generator

The rest of the ladder

This page has two of the eight emails. The Freelance Contract & Invoice Pack has the other six — the firm request, the escalation to AP, the final notice and the letter before action — plus the phone script, and the replies for "we pay on Net 60", "we can't pay until our client pays us", and a dispute raised only after the invoice went overdue.

Three contracts, a 25-clause library, and the invoice generator come with it. $29, one payment, no subscription.

→ Freelance Contract & Invoice Pack, $29